Integrate faster with AI

Let AI read the machine contract and draft a server-side adapter, then have your engineer validate it with the customer's complete handoff package and no dashboard access.

Official inputs for AI

OpenAPI 3.1Endpoints, schemas, authentication, and responses MarkdownComplete guide for a coding agent Event catalogValidate accepted events and versions llms.txtDocumentation and machine-resource index

Copy this prompt

You are a server-side integration engineer. Read these official MeetROAS resources first:
1. https://developers.meetroas.com/openapi.json
2. https://developers.meetroas.com/en/events.md
3. https://api.meetroas.com/v1/events/catalog

Generate the smallest integration for my server language: serialize the body once, calculate HMAC-SHA256 over timestamp + "." + raw_body, and pass the validation endpoint with HTTP 200 and valid=true. Never request or output a real Secret; keep it in a server-side environment variable.

Validation checklist

AI reads the OpenAPI, Markdown guide, and event catalog.
AI drafts only a server-side adapter and tests, without a real Secret.
The customer account Admin generates a separate account-level package for each destination and delivers it securely; the destination stores the Secret in its server-side secrets manager.
Call the validation endpoint and require HTTP 200 with valid=true.
Use the complete handoff's fixed test mrt_ with test: true for the full event sequence; go live with a real Campaign mrc_ only after Test Runs are healthy.

Never paste a Secret into a public AI chat, arbitrary web page, URL, support ticket, or log. You may certify it in the official MeetROAS playground's tab memory; production credentials must still be used only from your server-side secrets manager.