Integration
Connect DevITjobs UK to Apexverify
When something happens in DevITjobs UK, your agent does the next thing in Apexverify. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DevITjobs UK and Apexverify to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with DevITjobs UK and Apexverify
Triggers and actions 1 trigger · 6 actions
Trigger
New job postingPolls https://devitjobs.uk/job_feed.xml (GET, no auth, no params) and fires for each new job listing appearing in the XML feed. Feed item fields: title, company, location, salary, description. No unique job id is published in the feed — implementer must derive a stable polling identity (e.g. hash of title+company+location, or publish date if present) since the vendor exposes only this one unauthenticated read endpoint.
Action
Add batchUploads a list of email addresses or phone numbers as a new verification batch in Apexverify, and returns the new batch's id.
- Get batch details
Get detailed metadata/results summary for a batch by id. Endpoint: GET /v1/batch/{batch_uuid}/details.
- Get batch status
Get the processing status of a batch by id. Endpoint: GET /v1/batch/{batch_uuid}.
- List batches
List all verification batches on the account. Endpoint: GET /v1/batch.
- Normalize format
Normalize/standardize the format of a data item (e.g. phone/email) without full verification. Endpoint: POST /v1/format.
- Update batch parameters
Changes the verification settings on an Apexverify batch before it is launched, such as the contact type, target country, audience and caching rules.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.