Pidj API

What authentication does the Pidj API use?

The Pidj API uses HTTP Basic authentication with your account credentials. Through Jentic, these credentials are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw passwords directly.

Can I send bulk SMS messages with the Pidj API?

Yes. The /task/initiate endpoint triggers automated messaging workflows that send messages to groups of contacts. For individual messages, use the /send endpoint with a single recipient phone number.

How do I pause and resume a user account through the Pidj API?

Use POST /user/{id}/pause to temporarily suspend a user account and POST /user/{id}/unpause to reactivate it. The /user/{id}/recover endpoint handles account recovery scenarios.

How do I send an SMS through the Pidj API using Jentic?

Search Jentic for 'send business SMS message', load the /send operation schema, and execute with recipient phone number and message body. Jentic injects Basic auth headers automatically and returns delivery status.

Does the Pidj API support contact segmentation?

The API provides contact management through the /contact endpoints where you can create, retrieve, and update contact records. Contact grouping for targeted messaging is handled through the task initiation workflow.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Pidj operations and credentials the agent may use. Because Pidj carries the user and contact id in the URL path (/user/{id}, /contact/{id}), you can pin the agent to a single user and allow only read and send-message calls. State-changing operations like pausing or unpausing a user through /user/{id}/pause and /user/{id}/unpause stay out of reach unless you explicitly grant them.