Contacts

Contacts store the customer and supplier details that power invoices, purchases, subscriptions, and reconciliation. Use these mutations and queries to keep your CRM in sync or to enrich documents you create via the API.

Prerequisites

• A Naqood API secret or OAuth-issued secret scoped to the target organization
• The organization slug for every request
• A role that can manage contacts in that organization

Contact fields

Contact objects carry both commercial terms and basic profile data.

Field	Type	Notes
id	ID!	Stable identifier
name	String!	Display name used across documents
type	String!	Free-form label (for example company or individual)
email / phone	Email / String	Optional contact details
address...postalCode	String	Optional address lines
country / emirate / pOBox	Country / String	Regional details
companyId / vat	String	Registration numbers, when applicable
paymentTermType	String!	How due dates are calculated (days, current_month, etc.)
paymentTermDays	Int!	Days applied to the payment term
isCustomer	Boolean!	Marks the contact for sales flows
isSupplier	Boolean!	Marks the contact for purchase flows
account	Account	Optional default posting account
archived	Boolean!	Hides the contact without deleting it
isDeletable	Boolean	Helpful hint before calling deleteContact
createdAt / updatedAt	Timestamp!	Audit timestamps

Fetch a single contact

Retrieve the full contact profile when you have its ID.

query Contact($contactID: ID!) {
  contact(contactID: $contactID) {
    id
    name
    type
    email
    phone
    paymentTermType
    paymentTermDays
    isCustomer
    isSupplier
    archived
    account {
      id
      code
      name
    }
  }
}

List contacts

Page through contacts within an organization and apply filters or sorting.

query Contacts(
  $slug: Slug!
  $offset: Int
  $limit: Int
  $orderBy: OrderByInput
  $filter: JSONObject
) {
  organization(slug: $slug) {
    contacts(
      offset: $offset
      limit: $limit
      orderBy: $orderBy
      filter: $filter
    ) {
      count
      entries
    }
  }
}

• filter supports the standard operators (equalTo, notEqualTo, greaterThan, lessThanOrEqualTo, in, plus and/or groups).
• entries returns contact objects (same shape as Contact) as JSON blobs so you can hydrate your own models.

Create a contact

mutation CreateContact($input: CreateContactInput!) {
  createContact(input: $input)
}

CreateContactInput highlights:

Field	Required	Notes
slug	✅	Organization issuing the contact
name	✅	Display name
type	✅	Free-form label shown in the UI
paymentTermType	✅	days, current_month
paymentTermDays	✅	Number of days applied to the term
isCustomer	✅	true if the contact should appear in sales flows
isSupplier	✅	true if the contact should appear in purchasing
accountId	Optional	Default ledger account for postings
Address, tax IDs, and comms fields	Optional	Populate as needed

Example variables:

{
  "input": {
    "slug": "acme-co",
    "name": "Acme Supplies",
    "type": "company",
    "email": "billing@acme.test",
    "paymentTermType": "days",
    "paymentTermDays": 30,
    "isCustomer": false,
    "isSupplier": true,
    "accountId": "a42d5b18-aaaa-bbbb-cccc-1234567890ab"
  }
}

Update a contact

mutation UpdateContact($input: UpdateContactInput!) {
  updateContact(input: $input) {
    id
    name
    email
    paymentTermType
    paymentTermDays
    archived
  }
}

Provide the id plus the updated fields. Required properties (name, type, paymentTermType, paymentTermDays, isCustomer, isSupplier, slug) must still be present even when other fields are unchanged.

Archive, restore, or delete

• Archive: archiveContact(contactID: ID!) hides a contact from pickers without losing history.
• Restore: unarchiveContact(contactID: ID!) brings it back.
• Delete: deleteContact(contactID: ID!) permanently removes a contact that has not been used on journal entries. Check the isDeletable flag first to avoid conflicts.