Contacts API
Bring enquiries into Mango9 and keep contact details, notes and sales progress connected to your other tools.
In the CRM: Settings → Developer APIs → Contacts API
Keep the lead record connected
Use Contacts API when a website, advertising integration or another business system needs to pass customer details into Mango9. It can also read contacts, add notes and update their sales status.
For a marketing business, this means the phone number, enquiry details and campaign source can reach the team together. The agent can continue the conversation with useful context instead of retyping information from an email.
Match the action to the record
| Task | Endpoint | What it does |
|---|---|---|
| Read contacts | GET /api/contacts/get | Filter by search or group_id and use page and limit. Maximum 100 contacts per page. |
| Read one contact | GET /api/contacts/view | Use contact_id to read details, custom fields and notes. |
| Read setup lists | GET /api/contacts/groups, /fields or /statuses | Find the group IDs, field names and available sales statuses for the account. |
| Create / edit / remove | POST /api/contacts/create, /update or /delete | Create a record or act on the supplied contact_id. |
| Read / add notes | GET or POST /api/contacts/notes | Read notes or add a note for contact_id. POST /api/contacts/notes/delete removes a note by note_id. |
| Read / change status | GET or POST /api/contacts/status | Read or update the status for contact_id. |
Send the useful enquiry details
| Field | What to provide |
|---|---|
| key | The saved API secret belonging to this Mango9 account. |
| contact | The phone number, including its country code. Keep its format consistent across submissions. |
| name or first_name / last_name | The person’s name; email can be supplied separately. |
| address, city, state, zip, country | Location details collected by the enquiry form. |
| group_id | An existing group to organize the contact. |
| campaign_id | The intended lead campaign. A new contact with this value is submitted to that campaign’s routing rules. |
| source, note, lead_status | Where the enquiry came from, useful context and its starting sales status. |
| Custom fields | Use the account’s exact field_name values returned by /fields. Create the custom field in Mango9 before mapping data to it. |
Try a controlled contact submission
- Review the account’s lead-created workflows and the intended campaign routing before testing. Creating a contact can trigger those actions.
- Open Create Contact, paste the saved API key and enter your test contact’s phone number.
- Add the name, email and an existing Group ID if needed.
- Select Create Contact only when ready to save the test record.
- Retain the returned contact_id and find the record in Lead Fusion → Contacts. Confirm its fields and intended follow-up.
Handle an existing lead properly
The create endpoint returns err 97 when the same stored phone number already exists for the account. Find the existing contact and update it by contact_id instead of repeatedly creating it.
Creation accepts form fields or JSON. Successful responses use err 00 with data; missing and invalid keys use 01 and 02. Check the response body even when the HTTP status is 200.
Store the returned contact ID in your integration. This lets later notes, booking updates and sales-status changes stay attached to the correct person. Use a consistent phone format to reduce duplicate records.
Use it in a marketing campaign
A roofing enquiry can arrive with the postcode, project type and source form. A configured workflow can alert the team, arrange follow-up or start the next step. When campaign_id is included, the lead-routing engine applies the chosen campaign’s routing rules.
For a lead-selling business, prepare the buyers, campaign rules and delivery preferences before connecting the source. Creating the record successfully does not itself prove that a buyer accepted it; review campaign delivery and activity.