AdminConsole
API reference/Workmate Workforce
GETstatefullegacy-source evidence

To get the task list details.

/taskLists

These APIs follow OAuth2 based security. To know more about how to create your authorization tokens, please use our authorization token URL. More details available here. The API leverages OAuth 2.0 based security. Hence, the developer would need to send a request for an access token using their clientid and clientsecret to the OAuth API. Once validated from the OAuth API, the accesstoken and the tokentype need to be sent as Authorization header with the value: "{tokentype} {accesstoken}”. Authorization : tokentype accesstoken.

Build a requestGet credentials
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.

Request target

Call the operation

GEThttps://workmate.mapmyindia.com/apis/taskLists
Base URLhttps://workmate.mapmyindia.com/apis/
Authenticationoauth2 bearer
Journey roleobserve
Content typesNo request body
Path, query, and headers

Parameters

NameLocationTypeDescriptionExample
apiVersionrequired
headerstring

Header for this API. Available values are v1.0.0, Default value is v1.0.0

v1.0.0
Interactive, local, and credential-safe

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/taskLists
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/taskLists' \
  --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.

Five language quickstarts

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 /taskLists
curl --request GET \
  --url 'https://workmate.mapmyindia.com/apis/taskLists' \
  --header 'Authorization: Bearer YOUR_ACCESS_TOKEN'
Success and failure behavior

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
taskLists
array<object>

No field description in the source contract.

example
taskLists[].id
string

Unique Id of the task

32
taskLists[].name
string

Name of the task

Document Collection from client
taskLists[].description
string

Detailed description of task.

Collect documents like PAN Card, Passport and the application form.
taskLists[].taskListId
string

Unique Id number of the task list. It can be used while creating the Task

23
Response example
{
  "taskLists": [
    {
      "id": 32,
      "name": "Document Collection from client",
      "description": "Collect documents like PAN Card, Passport and the application form.",
      "taskListId": 23
    }
  ]
}
stateful integration

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.
Auditable source

Contract provenance

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