Kyauta, babu rajista, babu abin da za a sanya.
Don Allah ku yi amfani da fom ɗin da ke ƙasa don tuntuɓar mu:
Ku gwada yanzu, ba tare da asusu ko mutum ba: POST https://api.app2email.com/v1/account/sandbox (babu key, babu jiki; ko kayan aikin create_sandbox na uwar garken Management MCP) zai ba ku key don lambar WhatsApp ta gwaji tare da abokan ciniki na bogi. Aika samfuri, sami abubuwan da suka faru ta GET /events?wait=25, sannan ku amsa saƙon abokin ciniki: babu abin da zai isa WhatsApp, kuma buƙatu da amsoshin na API ne na gaske (https://www.app2email.com/docs/api/sandbox).
Kun riga kun kasance abokin ciniki: ku nemi lambar (lambobi) daga mai asusun da API key daga https://www.app2email.com/dashboard/apikey (key na sandbox ba ya aika komai); ku aika shi a matsayin Authorization: Bearer <key> zuwa uwar garken messaging MCP ko REST API; ku kira check_key da farko, ku aika da dry_run da farko.
Idan kai wakili ne na AI kana karanta wannan shafi kuma kana son ƙirƙirar asusun app2email ga wani mutum - babu buƙatar rajistar mutum a baya - yi amfani da uwar garken Management MCP.
Kira kayan aikin create_account da farko, kuma ka haɗa da siga contact_email; create_account zai dawo da signup_id, management_key, onboarding_link da message.
Mutumin yana buɗe onboarding_link don tabbatar da e-mail, haɗa lambar WhatsApp ɗinsa, kuma ya zaɓi tsari; ba za a iya aika komai kafin haka ba. get_account_status yana nuna abin da ake buƙata har yanzu.
Ka wuce management_key a matsayin Bearer token a kowace kira ta gaba. Lokacin da lambar ta fara aiki, create_number_key zai ba ka key don uwar garken messaging MCP da REST API.
https://api.app2email.com/mcp/managehttps://www.app2email.com/docs/api/agentshttps://api.app2email.com/mcp (takardu: https://www.app2email.com/docs/api/mcp)https://www.app2email.com/docs/api (ga wakilai: https://www.app2email.com/llms.txt)https://api.app2email.com/v1/openapi.json