Custom API & web services

Share Conrep data on your terms

Define API keys tied to applications and fields, issue short-lived tokens, and return JSON or XML to portals, vendors, and career sites. Job feeds use a separate client-scoped endpoint with search, pagination, and publish-requirement links from company settings.

Token & data requests JSON & XML Job & requirement feeds

Typical data export flow

1
Configure an API key

In API Settings, name the integration, pick the source application, choose exported fields, optional child records, and API conditions so only matching rows are returned.

2
Request a token

Call the custom data web service with your long-lived API key, company identifier, and a token request in JSON or XML. Conrep validates the key and returns a short-lived session token.

3
Pull records

Submit a data request using that session token to run the query tied to your key and receive records in the format you chose.

API Settings workspace

The API Settings module is where administrators build each integration: API Details, copy-ready URLs on API Keys, field selection, related child data, and API Calls/Log for troubleshooting.

API Details API Keys API Fields Childs Data API Calls / Log
Name & application Fields & conditions Copy endpoints Monitor calls
API Details

Give each key a name, tie it to a Conrep application module, and add a description. API Conditions use the same style of field filters as in-app searches so exports only include matching records.

API Keys tab

The RESTful Web Services tab provides copy-ready URLs for your environment, with documented parameters for token and data calls — API key, company identifier, request type, and response format.

API Fields & child data

Pick which columns appear in the payload and include related child records when partners need nested structures (for example line items or sub-records on a parent entity).

Integration Keys (company settings)

Company-level Integration Keys and publish-requirement links complement custom APIs — useful when you need a shareable job URL without building a full token flow.

Two service patterns in Conrep

Configurable exports for authenticated partners, plus job and requirement XML/JSON feeds scoped by client id.

Job & requirement web service

Client-scoped feeds for career pages, VMS-style integrations, and placement reporting. Call with your client identifier, request type, and filters for location, category, division, and dates.

  • Publish and detail requirements
  • Job search and job detail
  • Placement and submittable openings
  • Sorting and paged results

Career & publish links

Career pages and company settings can use the job web service and publish-requirement links so listings on your site stay in sync with open requirements in Conrep.

  • Posted-date windows and “all jobs” rules
  • Rich formatting in job descriptions
  • Division and category filters
  • Apply URLs embedded in job XML

Exact host names and identifiers are shown on your API Keys and Integration Keys screens after configuration — use those copy-to-clipboard values in production integrations.

What teams build with these APIs

Common patterns we see across staffing, healthcare, and professional services customers.

Client portalsPlacement & job status
Career sitesLive job search
Vendor VMSRequirement publish
BI & warehousesScheduled exports
Mobile appsJSON payloads
Legacy XMLEnterprise adapters
Scoped exportsAPI conditions
Field controlAPI Fields tab

Security, format, and operations

Two-step token model

Long-lived API keys never expose raw database access to callers. A token request proves the key; a data request requires the short-lived token so automated jobs can rotate credentials safely.

JSON and XML

Choose JSON for modern consumers or XML when an upstream system expects element-based payloads — the same key definition drives both.

API Calls / Log

Review call history from API Settings when a partner reports empty results or auth errors — without turning on verbose logging on production app servers.

Application-scoped keys

Each key is bound to a Conrep application module at creation time, keeping exports aligned with the tables and security model that module already uses.

Job feed filters

The job feed service supports city, state, zip, job category, division, how far back jobs were posted, and sort or page parameters for large job boards.

Placement exports

Placement-style requests return assignment and status data for client reporting when client and division filters match your integration agreement.

Common questions

Where do I find my API URLs and keys?

Open API Settings for the key you created, go to the API Keys tab, and use the copy icons next to each RESTful Web Services URL. The screen lists your API key, company identifier, request types, and formats for both token and data calls in JSON and XML.

What is the difference between the custom data API and the job feed API?

The custom data web service serves API keys you configure (any supported application and field set). The job and requirement service is the standard listing and placement feed scoped by client — used heavily by career pages and publish-requirement integrations.

How do I limit which records are exported?

Use API Conditions on the API Details screen to attach field-condition filters. Combine them with the fields you select on API Fields and any child data definitions so partners only see rows that match your business rules.

Can I publish jobs without the token API?

Yes. Company Integration Keys and publish-requirement links (from general company settings) provide shareable URLs for job listings. Many sites call the job web service directly with a known client id and request type.

Is SOAP still supported?

Some legacy SOAP-style endpoints may still exist in older deployments. New integrations should use the REST-style HTTP URLs documented on the API Keys tab for token-based data and job feeds.

Walk through API Settings on a demo

We can configure a sample key, copy token and data URLs, and show a live job feed from a career page workflow.

Book an API walkthrough

Integrate Conrep with your stack

Schedule a demo to see custom API keys, token-based exports, and job web services configured for your company.

Menu