Updates shipped from September 4, 2026, through October 30, 2026.

Connect your AI assistant to Crelate with more confidence. Since September 4, we have released a round of MCP server and API v3 updates, shaped directly by feedback from early users. Your connected assistant can now give more reliable answers, ask more precise questions, and read the resumes in your database.

These updates are for Admins who manage MCP connections, recruiters who work with a connected assistant, and developers who build on API v3.

At a Glance

More reliable answers. Unsupported requests are flagged instead of quietly returning unfiltered results.
More precise questions. Filter by owner, by business dates, by Company, by distance, and by tag name.
Readable resumes. Your assistant can review a shortlist based on what the resumes actually say.
Easier and safer connecting. Connections stay signed in, ChatGPT is supported, and Admins have more control.
A new default page size. The default is now 100 records per page. If your integration relies on the old default, see Before You Upgrade.

Answers You Can Trust

Clearer feedback on requests. When a request includes something Crelate does not support, the response now says so instead of quietly returning unfiltered results. When an assistant sends an invalid sort, filter, or page size, the error lists the values that are allowed.
Optional strict mode. Teams that prefer to reject unsupported requests outright can turn on strict mode.

Ask for Exactly What You Need

Filter by owner. Ask about only your own activities, Jobs, Contacts, or placements. A question such as “How many calls did I make yesterday?” no longer needs to pull everyone’s activity.
Filter by the dates that matter. Search by when an activity or placement happened, when a Job opened or closed, or when a Contact or Company was created, in addition to when a record was last modified.
Contacts at a Company. Retrieve the current Contacts at a Company, with the option to include people who used to work there.
Radius search on Contacts. Find Contacts within a set distance of a location, matched against any address on the record.
Find a tag by name. Look up a single tag without downloading the whole list.
Worksite details included. Worksite information now comes back with Companies and Jobs by default, and with placements on request.

Read Resumes and Documents

Resume and document text now comes back clean and readable. Your assistant can review a shortlist based on what the resumes actually say.

Easier and Safer Connecting

Connections stay signed in when a session expires, so you are no longer asked to reconnect.
Consent screens are easier to read.
You can now connect from ChatGPT.
Organizations that enable MCP now start with read-only connections by default. You can opt in to tools that write data for the connections that need them. Existing connections are unchanged.
Actions that an assistant performs on your data now show the assistant’s name in the audit log.

More Control for Admins

Admins can grant MCP access separately from API access.
A new MCP overview page for Admins includes a link to the feedback board.

Sign in with OAuth

New legacy MCP keys can no longer be generated. Connect by signing in with your Crelate credentials instead, with no key to create, copy, or paste. Your connected assistant acts on your behalf and can only access what your Crelate user account is already authorized to access.

If you already use a legacy MCP key, it continues to work, and you do not need to change anything. If you would like to move to the new experience:

In Crelate, navigate to Your Profile & Preferences and select AI / MCP Access.
Next to your existing connection that uses the previous MCP key method, select Revoke.
Reconnect your AI assistant by signing in. For step-by-step instructions, see Setting Up Your Crelate MCP Connection.

If you do not see AI / MCP Access in Your Profile & Preferences, ask your Crelate Admin to confirm that the MCP Access privilege is enabled for your role. Older setup instructions that rely on legacy keys no longer work for new connections.

For Developers and API Users

Unsupported parameters are reported. The response includes an Errors[] entry with Type: "IgnoredParameter" and Code: 200. To check whether a request actually failed, test Errors.some(e => e.Code !== 200) rather than Errors.length > 0, because the new entry is a warning and not a failure.

Strict mode. Add validation=strict to any request to have unsupported query parameters and unrecognized JSON body fields rejected with a 400 that lists each one. Strict mode is optional. By default, unsupported requests return the warning described above.

New date filters. These can be combined with modified_after and modified_before.

Records	New filters
Activities and placements	`when_after`, `when_before`
Jobs	`opened_after`, `opened_before`, `closed_after`, `closed_before`
Companies, Contacts, and stage history	`created_after`, `created_before`

Contacts at a Company. A new endpoint and MCP tool return the current Contacts at a Company. Pass include_former=true to include people who used to work there.

Resume and document text. Requesting a document’s extracted text with content_mode=4 now returns clean, readable text instead of corrupted characters. Document content requests also now honor the mode parameter.

Larger pages. Large scans need about half as many calls.

	Before	Now
Maximum records per page	100	200
Default records per page	50	100

Data consistency fixes.

Workflow statuses show whether a stage counts as open.
Jobs can be sorted by open date, and placements by placement date.
Company account manager and relationship manager values now appear as names.
Email activities link to the record they are about.
Job posting search accepts limit and fields.
Field names and activity content fields are documented more consistently.

Before You Upgrade

The default page size is now 100. If your integration relies on the old default of 50, for example by stepping through results 50 at a time or by treating a 50-record page as the last page, set limit explicitly. If your integration already sets a limit, nothing changes. You can request up to limit=200 for fewer calls.

Share Your Feedback

These updates came from the people using MCP and API v3 every day. If you have an idea, request, or workflow you would like to see improved, share it on our Feedback Board so our Product team can review it for a future release.

Share Your Feedback!