# Authentication URL different than Connection Base URI

**URL:** <https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194>\
**Category:** Integrator.io\
**Tags:** connection, authentication, http\
**Created:** [March 14, 2024, 6:47pm UTC](https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194 "2024-03-14T18:47:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![marceloborges](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/marceloborges/32/9594_2.png) [@marceloborges](https://connective.celigo.com/u/marceloborges)\
**Post date:** [March 14, 2024, 6:47pm UTC](https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194/1 "2024-03-14T18:47:37Z")

</div>

Hello,

It seems Celigo doesn't have any out-of-box capabilities to integrate with Plytix PIM API, so, I think I need to make use of some of those universal HTTP connectors.

I'm trying to follow this help article:

[Set up a token-based HTTP connection – Celigo Help Center](https://docs.celigo.com/hc/en-us/articles/360045127771-Set-up-a-token-based-HTTP-connection)

The very first thing I'm having issues with, is that the Authentication URL for this API is [https://auth.plytix.com/auth/api/get-token](https://auth.plytix.com/auth/api/get-token), whereas the Base URI for the rest of the whole API is [https://pim.plytix.com/api/v1/](https://pim.plytix.com/api/v1/)

How can I setup this Token Based Connector to get the Token from one URL, and actually have all the other flows work with the base URI [https://pim.plytix.com/api/v1/](https://pim.plytix.com/api/v1/)?

And then my second question, is that Plytix asks us to send an API Key and Password through a POST call, but I didn't find anything on the Token authentication that lets me add a Body to be sent via POST.

Anyone that can assist me in getting this connection setup?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [March 14, 2024, 8:34pm UTC](https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194/2 "2024-03-14T20:34:19Z")

</div>

@marceloborges the field name and relative text underneath is a little misleading, but the relative url field under the refresh token section allows a full url. There is a note in that KB article you linked.

 ![5301043caa20740200000001-520e8cf189de465ebe4fcf271a820019.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/a/a23c265bbc22fc6c28e5c7ff94638c245c1abee6.png)

---

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [March 14, 2024, 8:42pm UTC](https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194/3 "2024-03-14T20:42:56Z")

</div>

@marceloborges should look something like this. You should put your key and password in the encrypted field and then reference the encrypted field with handlebar expressions in the post body.

 ![5301043caa20740200000001-5824110b1b7d41ffad6b22b1eba2e97a.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/4/4ddb9837a42b3ffd73ad37425dcefea331ea4ff8.png)

 ![5301043caa20740200000001-ee56da19d35f4876877fec1f0ec4cfff.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/c/c643dd29be83b133121e7f3bd01df18409c4d665.png)

 ![5301043caa20740200000001-0dc71aa3b28d4fb2963ea11741dff287.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/f/f14fe7bbf267a2fd35444743688acd174400cbb1.png)

 ![5301043caa20740200000001-2996be9b1d36495d9e003f7cc1c55ec1.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/4/4e2deb2963be94df5bc9650c4a490fa63fb76fa2.png)

Encrypted field:

```
{"api_key": "value","api_password": "value"}
```

Post body:

```
{ "api_key": "{{connection.http.encrypted.api_key}}", "api_password": "{{connection.http.encrypted.api_password}}"}
```

---

<div class="post-metadata">

**Author:** ![marceloborges](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/marceloborges/32/9594_2.png) [@marceloborges](https://connective.celigo.com/u/marceloborges)\
**Post date:** [March 15, 2024, 1:34pm UTC](https://connective.celigo.com/t/authentication-url-different-than-connection-base-uri/194/4 "2024-03-15T13:34:08Z")

</div>

@tylerlamparter thank you so much. This very detailed screenshots helped me through the process now. I was just confused between the Token and the Refresh Token parts of the setup. But understanding that I could include a whole different URL for authentication purposes, that made the difference and I really haven't paid attention to on the article. Tks tons!