API reference/Workmate Workforce
GETstatefullegacy-source evidence

To get the form's Id and their details from your account.

/configurations/forms

It gives all the forms which are created under your account. using this API you can get the unique Ids of different form and it can be used in custom form data API.

Legacy contract evidence

This operation was normalized from a MapmyIndia-generation specification. Validate its current Mappls host, path, package entitlement, authentication generation, and commercial availability before production use.

Call the operation

GEThttps://workmate.mapmyindia.com/apis/configurations/forms
Base URLhttps://workmate.mapmyindia.com/apis/
Authenticationoauth2 bearer
Journey roleobserve
Content typesNo request body

Parameters

NameLocationTypeDescriptionExample
apiVersionrequired
headerstring

API version should be mentioned in the header along with bearer Token. Available version is v1.0.0, Default version is v1.0.0

v1.0.0

Build your request in eight languages

Change source-backed examples once, validate required inputs, and copy the synchronized cURL, JavaScript, Python, Java, C#, Go, PHP, or Ruby request. Credentials remain environment references, and this page never sends a provider request.

Local request composerCode stays local · fixtures are explicit
GETRequest inputs
1 editable · 0 protected
Generated in eight languages
Environment-backed credentials
GEThttps://workmate.mapmyindia.com/apis/configurations/forms
Credential-free sandboxExecute this contract without a provider call
How fixtures work
Generated from your inputs
curl --request GET \
  --url 'https://workmate.mapmyindia.com/apis/configurations/forms' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_ACCESS_TOKEN}"

Credential-safe by constructionSet MAPPLS_ACCESS_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Send a production-shaped request

Examples use environment-backed access tokens, explicit timeouts where supported, status checks, and JSON bodies derived from the source schema. Replace sample identifiers and coordinates with values from your application.

GET /configurations/forms
curl --request GET \
  --url 'https://workmate.mapmyindia.com/apis/configurations/forms' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'

Responses

200

default response

204

Content Not available.

400

Bad Request - Invalid ID supplied or invalid data type.

401

Unauthorized Request. Access to API is forbidden.

403

User type is Field user. Only manager and admin type user have the access to this API

404

Not Found - URL Not Found

200 response fields

FieldTypeDescriptionExample
forms
array<object>

No field description in the source contract.

example
forms[].formId
string

Forms unique ID, Which will be used in Custom Forms data API to get the details.

5bb5e97a390bec703259364d
forms[].formName
string

Name of the Form.

Delivery Details
forms[].formDescription
string

Detailed description of the Form

Enter the delivery details while doing checkout
Response example
{
  "forms": [
    {
      "formId": "5bb5e97a390bec703259364d",
      "formName": "Delivery Details",
      "formDescription": "Enter the delivery details while doing checkout"
    }
  ]
}

Operate it safely

observe

This operation observes durable platform state. Preserve resource identifiers and account for pagination, delay, and eventual consistency.

Keep credentials and raw tokens out of source, client bundles, prompts, and logs.Record the operation ID, status, latency, retry count, and source contract version in traces.Classify 4xx responses before retrying; back off and add jitter for retryable 5xx or transport failures.Persist resource identifiers and apply commands exactly once in effect across retries and event replay.

Contract provenance

Source file
contenthub/dochub/mapmyindia-workmate-apis/custom/Company-Configurations.json
SHA-256
e5d6101b29f0c3ebb3c3191472423b61b80757b15266721c0c72961804669f97
Normalization
Fields are parsed from OpenAPI. Operational guidance and language samples are generated and labeled separately.