What authentication does the PIMMS API use?

The PIMMS API uses Bearer token authentication. Your API token is passed in the Authorization header. Through Jentic, this token is stored encrypted in your Jentic One instance and injected automatically into requests.

Can I create tracked links with campaign attribution parameters?

Yes. The POST /links endpoint accepts a destination URL along with campaign, source, and medium parameters. The generated tracked link records all clicks with full attribution data for later analysis.

What analytics data does the PIMMS API return?

The GET /analytics endpoint returns click counts, referrer information, and temporal engagement patterns for your tracked links. You can filter by campaign, date range, and link to measure performance across marketing channels.

How do I create a tracked link through the PIMMS API using Jentic?

Search Jentic for 'create tracked marketing link', load the /links operation schema, and execute with your destination URL and campaign parameters. Jentic handles Bearer token injection and returns the generated tracked link URL.

What is the difference between the /links and /links/upsert endpoints?

POST /links always creates a new tracked link. PUT /links/upsert creates a link if it does not exist or updates the configuration if one already exists for that destination URL. Use upsert to avoid duplicate tracked links for the same content.

Can I limit what my agent is allowed to do with the PIMMS API?

Yes. Because you run Jentic One yourself, your own rules decide which PIMMS operations and credentials the agent may use. PIMMS scopes by operation rather than by resource id, so you grant only the calls the agent needs, such as POST /links to create a tracked link or GET /analytics to read click data. If you do not want the agent overwriting existing links, you simply leave the PUT /links/upsert operation out of the set it can call.