Authentication

The idibu Posting API utilizes a hash-based authentication method, designed for whitelabel partners managing multiple Client accounts. To authenticate API requests for a specific Client, you'll need to include that client account's hash value directly within the API endpoint URL.

Understanding and obtaining hashes

Each Client account managed by your system has a unique client hash (client-hash). This hash serves as the primary authentication token for actions performed on behalf of that Client through the Posting API.

The system generates client hashes when you create client accounts via the Service Management Webservice. As a whitelabel partner, you will use your partner credentials - partner-password and exempt-it - to manage these Client accounts and retrieve their respective hashes. Please refer to the webservice's documentation for detailed information on account creation and hash retrieval.

Authenticating Posting API requests

To authenticate your Posting API requests for a specific Client, include the hash value directly within the API endpoint URL; partner-password and exempt-it are not required for these requests.

Endpoint

With the above in mind, for all requests that involve creating Jobs and their corresponding Posts, the endpoint will always be:

https://ws.idibu.com/clients/api/REMOTE/V3/[client-hash]

with the XML posting data provided as an xml_text POST parameter, UTF-8 and URL-encoded as the application/x-www-form-urlencoded data type.