API and agent integration
Build with your code. Or your coding agent.
Build native Apple conversations from your application or with an agent connected to Bird. Create content, connect journeys and operate the customer exchange through the same business identity, permissions and service context.
Explore Apple Messages for BusinessOne complete native exchange
EXAMPLE01 · Business
Approved identity
02 · Conversation
Customer context
03 · Native message
Useful content
04 · Response
Connected action
Fictional integration and agent workflow. The example controls do not publish a real journey. Use the API contract for exact fields and permissions.
A native experience, connected to your application
Keep the conversation close to the business action.
Your application knows which appointments are available and when a booking is confirmed. Bird connects that business logic to the Apple Messages conversation: send native content, receive the customer’s response and return the result of the action they chose.
Build with your API client or a coding agent connected through Bird’s MCP server. Use the published operation contract and scoped workspace permissions to inspect businesses, prepare content and connect customer journeys to your application.
Read the integration guideBuild the complete exchange.
Treat the integration as a conversation with a result. Keep its references intact across the native response, application request and customer confirmation.
Resolve the business and conversation
Use the intended workspace and approved Apple business with credentials scoped to the operation. Ordinary replies use the open conversation’s Apple identity; phone-addressed invitations follow their separate approved contract.
Send native content with a defined response
Choose the content type and expected answer. Preserve the message, request and conversation references so a list selection, form submission or time choice can be matched to the intended next step.
Validate and perform the business action
Check the response against current business data and customer permissions. Use your booking, commerce or identity application to carry out the action, with that application’s authorization and recovery behavior.
Return the recorded outcome
Correlate the result and continue the conversation. If an observation repeats or arrives late, resolve it against the existing operation; keep an accepted send separate from the business outcome the customer is waiting for.
Give a coding agent the same clear contract.
Inspect and prepare with real context
Connect the agent to Bird’s MCP server and provide the relevant integration guide, workspace and redacted business model. Have it inspect existing configuration before preparing content or changes, and keep credentials in the execution environment.
Review the change before publishing
Inspect the exact native messages, journey branches and connected actions. Test a successful exchange and a materially different refusal or uncertain result, then publish the reviewed revision with the permissions your team has approved.
API and agent integration questions
Can we copy an Apple gateway request directly into Bird?
Can a coding agent build and operate the experience?
Can a coding agent read the product guides?
What should the first integration test prove?
Build the connected journey
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Connect the exchange to a real result.
Review your application, permitted operations and test plan with an Apple Messages specialist. Prove the reply and recovery paths before launch.