1.png){kind=small}
Client project requests
An authenticated client can submit a structured project request for feasibility, pricing and launch review. Creating the request does not automatically confirm supply or open fieldwork.
Connected research operations
Connect the project, the participant and the returned outcome.
Useful integration starts with shared definitions. Discuss the project information, routing identifiers and outcome messages your systems need to exchange, then test the agreed connection before production traffic begins.
01 / API & Integrations
Choose the connection that solves the operating problem.
Supported paths serve different responsibilities. Access depends on an approved account, enabled permissions and the agreed project scope.
Project information and supplier access
Approved connections can retrieve permitted project information. Supplier access, acceptance and routing links follow the account and project access rules.
Returned survey outcomes
Supported callbacks associate an outcome with a participant identifier. Success, failure, quota, quality-failure and duplicate returns must have consistent meanings across the agreed journey.
02 / API & Integrations
Agree the contract before connecting systems.
A short technical working session should resolve the items that can otherwise create ambiguous delivery records.
Identifiers and permitted fields
Map project codes, participant IDs and external references. Decide which system owns each field, what is required and which information should stay out of URLs.
Access and changes
Agree the approved account, credential handling, permission scope, error responses and rate-limit behaviour. Share credentials through the agreed secure channel rather than a public enquiry form.
Retry and reconciliation rules
Test repeated messages and delayed returns. Request identifiers can support replay handling on the supported project-creation path; retry behaviour for each endpoint needs to be confirmed separately.
03 / API & Integrations
Prove the journey with test records.
Check qualified entry, screen-out, quota-full and completion paths, together with missing or mismatched identifiers. Record the expected response and the owner of any unresolved result.
A return is part of the evidence
A callback records the returned event; client validation and configured quality review still affect the reconciled outcome. Keep provisional, reviewed and accepted delivery distinct.
External visibility has a scope
Progress inside a client-hosted survey, activity events or resume links require a suitable agreed integration. Routing alone does not reveal every external page or action.
Continue with context
Connect the information with your actual study.
Share your audience, markets, method, target completes, LOI and timing. We can discuss practical options, assumptions, responsibilities and the handover your team needs.