# Accessing Real Time trips API through Power BI

**URL:** <https://opendataforum.transport.nsw.gov.au/t/accessing-real-time-trips-api-through-power-bi/1974>\
**Category:** Uncategorized\
**Created:** [April 19, 2020, 1:31am UTC](https://opendataforum.transport.nsw.gov.au/t/accessing-real-time-trips-api-through-power-bi/1974 "2020-04-19T01:31:24Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jayen](https://sea1.discourse-cdn.com/flex019/user_avatar/opendataforum.transport.nsw.gov.au/jayen/32/208_2.png) [@jayen](https://opendataforum.transport.nsw.gov.au/u/jayen)\
**Post date:** [April 20, 2020, 6:28am UTC](https://opendataforum.transport.nsw.gov.au/t/accessing-real-time-trips-api-through-power-bi/1974/4 "2020-04-20T06:28:49Z")

</div>

ok, so it sounds like there was a connection issue on the first laptop, and you got further on the second laptop.

the Authorization header value is formatted with the word “apikey”, then a space, then the actual API key. There is an example here: [Using an API Key](https://opendataforum.transport.nsw.gov.au/t/using-an-api-key/212)

Do you know if Power BI is setting the Authorization header as required by the API? It may just be setting it to the API key (without the word “apikey”).

---

_[View the full topic](https://opendataforum.transport.nsw.gov.au/t/accessing-real-time-trips-api-through-power-bi/1974)._