Can I create candidates and attach them to a job through the Manatal API?

Yes. POST /open/v3/candidates creates a candidate record, and the candidate can be associated with a job through the candidate payload's job reference fields. Use PUT /open/v3/candidates/{candidateId} afterwards to update stage or attach activities.

What are the rate limits for the Manatal API?

The published spec does not list explicit rate limits. Manatal's public docs note that excessive request rates may be throttled at the workspace level. For bulk imports, batch and back off on 429 responses rather than hammering the candidate or job endpoints.

How do I post a new job to Manatal through Jentic?

Run pip install jentic, then search Jentic for 'create a job in manatal'. Jentic returns the POST /open/v3/jobs operation, you load its input schema, and execute with the title, description, and client_id fields populated to create the job.

Does the Manatal API expose pipeline stages?

Yes. GET /open/v3/pipelines returns the pipelines configured in the workspace, including the ordered stages. This is how external tools can map their internal candidate statuses onto the correct Manatal stage when syncing records.

Can I retrieve the activity history of a candidate?

Yes. GET /open/v3/candidates/{candidateId}/activities returns the timestamped activity events for a single candidate, which is what funnel reports and recruiter dashboards consume to reconstruct touchpoints.

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

Yes. Because you run Jentic One yourself, your own rules decide which Manatal operations and credentials the agent may use. Since Manatal puts the job or candidate id in the URL path, such as /open/v3/jobs/{jobId} and /open/v3/candidates/{candidateId}, you can pin the agent to a single record so it only reads and updates that job or candidate. You also choose the operations it may call, so write actions like creating jobs or candidates are excluded unless you explicitly allow them.