Datascope is a mobile field data collection and operations platform for digitizing inspections, audits, work orders, safety checklists, and quality control. Teams complete customizable mobile forms — even offline — with photos, signatures, and geolocation, available in real time. Its API exposes locations, form answers, task assignments, tickets, and generated files.
Power end-to-end data operations for your Datascope API with Nexla. Our bi-directional Datascope connector is purpose-built for Datascope, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Datascope or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Datascope workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to DataScope, you need a DataScope account with API access enabled and your personal API key. The DataScope External API uses API key authentication — every request must include your API key in the Authorization request header.
Keep your DataScope API key confidential. Anyone with access to the key can make API requests on behalf of your account. If you believe your key has been compromised, regenerate it from the DataScope Integrations settings immediately.
Authenticate using your Datascope API key in the Authorization header. The Authorization header is the documented and supported authentication mechanism for the External API.
Field
Required
Secret
Description
API Key Value
Yes
Yes
An encoded string value used as a secret token to authenticate API requests
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your DataScope API key in the API Key Value field. This is the key you copied from the DataScope Integrations settings (see Prerequisites above). The key is passed in the Authorization request header for every call to the DataScope External API, authenticating Nexla and authorizing access to your account's data.
The DataScope API key is a sensitive credential. Nexla stores this value securely and uses it only to authenticate requests to the DataScope External API on your behalf.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Datascope connector tile, then select the credential that will be used to connect to the Datascope account, and click Next; or, create a new Datascope credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Datascope endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List Locations
Returns a list of all locations available in your Datascope account. Use this endpoint to retrieve the full catalogue of locations defined in Datascope, which are used to assign tasks, associate form answers, and organize field operations geographically.
This endpoint requires no additional configuration parameters beyond selecting the template. Nexla will automatically retrieve all locations from your account using offset-based pagination, fetching up to 200 records per page.
Each location record typically includes the location name, code, address, coordinates (latitude and longitude), and associated contact and company information.
Location data is foundational for many Datascope workflows. Use the List Locations endpoint to build a directory of your operational sites before joining location IDs returned by other endpoints (such as List Answers) to their full location details.
List Answers (v2 - flat format)
Returns all form answers collected in your Datascope account in the v2 flat format, where each row represents a single answer to a single question. This is the preferred endpoint for analytical and data pipeline use cases because the flat structure integrates directly with tabular data destinations such as databases and data warehouses.
This endpoint requires no additional configuration parameters beyond selecting the template. Nexla will automatically retrieve answers using offset-based pagination, fetching up to 200 records per page.
Each record includes the form name, form ID, submitting user details, timestamps, GPS coordinates, location assignment, and the individual question-answer pair.
The v2 flat format is recommended over the v1 nested format for most analytical pipelines because each row contains a single question-answer pair, making it easier to filter, aggregate, and join with other data. Use the List Answers (v1 - nested format) endpoint only if your pipeline requires the legacy grouped structure.
List Answers (v1 - nested format)
Returns form answers in the legacy v1 nested format, where answers are grouped by form submission rather than returned as individual question-answer rows. Use this endpoint when your analytical pipeline depends on the form-grouped structure or when integrating with systems built against the original Datascope API format.
This endpoint requires no additional configuration parameters beyond selecting the template. It returns a static (non-paginated) response.
Note that the v1 endpoint has a 600-record cap. For accounts with large volumes of submissions, use the List Answers (v2 - flat format) endpoint to retrieve complete data sets without this limitation.
The v1 endpoint is provided for backward compatibility. For new pipelines, the v2 flat format endpoint is recommended, as it supports full pagination and returns data in a structure that is easier to work with in most analytical tools.
List Metadata Objects
Returns the full catalogue of metadata list elements in your Datascope account, such as products, clients, or any other custom list types your organization has defined. Metadata objects are used in Datascope to standardize dropdown options and reference data across forms.
This endpoint requires no additional configuration parameters beyond selecting the template. The full result set is returned in a single response without pagination.
Each metadata object record includes the element name, code, description, and any custom attributes defined for the list type.
Use this endpoint to extract your Datascope reference data for use in lookups or to enrich other data sources. To retrieve a single specific metadata element by its type and ID, use the Get Metadata Object endpoint instead.
List Notifications
Returns a list of all notifications generated for your Datascope account. Notifications in Datascope are alerts triggered by form submissions or other events, and can be used to monitor field activity, flag anomalies, or track compliance issues in real-time.
This endpoint requires no additional configuration parameters beyond selecting the template. Nexla will automatically retrieve all notifications using offset-based pagination, fetching up to 200 records per page.
Get Metadata Object
Retrieves a single metadata list element by its metadata type and ID. Use this endpoint to resolve specific list item references returned by other Datascope endpoints (such as List Metadata Objects or form answers that include list IDs).
This endpoint requires the following parameters:
Metadata Type: Enter the name of the metadata list (list type) that the element belongs to. This corresponds to the metadata_type field in the Datascope API. For example, if your account has a list named "products", enter products.
Metadata ID: Enter the numeric ID of the specific metadata list element you want to retrieve. This ID is returned by the List Metadata Objects endpoint and is referenced as list_id in form answer records.
Use the List Metadata Objects endpoint first to identify the correct metadata type name and element IDs before configuring this endpoint. The Get Metadata Object endpoint is useful for resolving individual list item references without downloading the entire catalogue.
List Files
Returns the most recently generated files in your Datascope account, such as PDF reports and data exports produced by Datascope's reporting features. Use this endpoint to track or download output files generated from form submissions and scheduled reports.
This endpoint requires no additional configuration parameters beyond selecting the template. The result set is returned in a single response without pagination.
Each file record includes metadata such as the file name, type, URL, and creation date. Optional start and end query parameters can be used in manual configuration to narrow results by date range.
This endpoint returns metadata about generated files, not the file content itself. To retrieve the actual file content, use the file URL provided in the response to download the file directly.
List Task Assigns
Returns task assignments for your Datascope account by period. Task assignments represent work items assigned to specific users for completion at a given location on a specified date. Use this endpoint to monitor field team workloads, track assignment completion rates, and integrate task data with workforce management or scheduling systems.
This endpoint requires no additional configuration parameters beyond selecting the template. Nexla will automatically retrieve task assignments using offset-based pagination. The default page size is 100 records, with a maximum of 300 records per page.
The response includes a nested structure containing a task_assigns array along with total, limit, and offset pagination fields. Nexla uses the task_assigns array as the source of individual records.
Get Task Assign
Retrieves a single task assignment by its numeric ID, including detailed assignment fields. Use this endpoint to fetch complete information about a specific task assignment when you know its ID.
This endpoint requires the following parameter:
Task Assign ID: Enter the numeric ID of the task assignment to retrieve. Task assignment IDs are returned by the List Task Assigns endpoint.
Use the List Task Assigns endpoint first to identify task assignment IDs, then use Get Task Assign to retrieve full detail records for specific assignments.
List Tickets (Findings)
Returns tickets (also called findings) from your Datascope account filtered by period, status, and form. Tickets in Datascope are issues or non-conformances identified during inspections or audits that require follow-up action. Use this endpoint to track open issues, monitor resolution progress, and integrate ticket data with quality management or CAPA (corrective action and preventive action) systems.
This endpoint requires no additional configuration parameters beyond selecting the template. Nexla will automatically retrieve tickets using offset-based pagination, fetching up to 200 records per page with a maximum offset of 2,000.
Optional filters for status and task_form_id can be applied using manual configuration to narrow results to specific ticket types or form sources.
The pagination limit for this endpoint is a maximum of 200 records per page with a maximum offset of 2,000. For accounts with very large ticket volumes, consider filtering by date range or status to retrieve data in manageable segments.
Get Ticket (Finding)
Retrieves a single ticket (finding) by its numeric ID. Use this endpoint to fetch the complete detail record for a specific ticket, including all fields and status information, when you know its ID.
This endpoint requires the following parameter:
Ticket ID: Enter the numeric ID of the ticket (finding) to retrieve. Ticket IDs are returned by the List Tickets (Findings) endpoint.
Use the List Tickets (Findings) endpoint first to identify ticket IDs, then use Get Ticket (Finding) to retrieve the complete record for a specific ticket.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Datascope data sources can also be manually configured to ingest data from any valid Datascope External API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Datascope External API endpoints begin with https://www.mydatascope.com/api/external/ and use the GET method for reads—for example, https://www.mydatascope.com/api/external/v2/answers for the List Answers (v2) endpoint. Most endpoints return a top-level JSON array, so the path to data is typically $[*]; the List Task Assigns endpoint is an exception, returning a nested task_assigns array (path to data $.task_assigns[*], with total, limit, and offset available as metadata). You do not need to add an Authorization header manually—it is applied automatically from your Datascope credential.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Datascope data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Datascope destination, and select the Send to Destination option from the menu. Select the Datascope connector from the list of available destination connectors, then select the credential that will be used to connect to the Datascope account, and click Next; or, create a new Datascope credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Datascope endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Change Form Answer
Modifies a previously submitted form answer in Datascope. Use this endpoint to update specific question values in existing form submissions — for example, to correct data entry errors, update statuses, or enrich answers with information from other systems.
The request body must contain the following fields to identify and update the target answer:
form_name: The name of the form that contains the answer to be modified.
form_code: The unique code identifying the specific form submission.
question_name: The name of the question whose answer should be modified.
question_value: The new value to set for the specified question.
subform_index (optional): If the question belongs to a subform (repeating section), specify the index of the subform instance to target.
Ensure that the field names in your Nexset match the expected body fields above, or use Nexla's data transformation features to map your data to the required structure before sending to this endpoint.
This endpoint modifies an existing form submission — it does not create new submissions. Ensure that the form_code value in your data corresponds to an existing submission in your Datascope account.
Create Location
Creates a new location in your Datascope account. Use this endpoint to programmatically add locations — such as customer sites, inspection points, or store branches — from data in another system, keeping your Datascope location catalogue in sync with your source of truth.
The request body should include the following fields:
name: The display name of the new location (required).
code: A unique identifier code for the location.
address: The street address of the location.
latitude and longitude: GPS coordinates of the location, enabling geolocation features in the Datascope mobile app.
Contact fields: Contact name, phone, and email for the location.
Company information (optional): Company name and related fields if the location is associated with a specific organization.
Ensure that your Nexset contains a record for each location to be created, with fields mapped to the expected structure above.
Update Location
Updates an existing location in your Datascope account by its numeric ID. Use this endpoint to keep location records current when address, contact, or company details change in your source system.
This endpoint requires the following configuration parameter:
Location ID: Enter the numeric ID of the Datascope location to update. Location IDs can be retrieved using the List Locations data source endpoint. This ID is appended to the API URL to target the specific location record.
The request body fields mirror the Create Location payload (name, code, address, latitude, longitude, contact details, and optional company information). Include only the fields that need to be updated.
Use the Datascope List Locations source endpoint in Nexla to retrieve current location IDs before configuring this destination. The Location ID must correspond to an existing location in your Datascope account.
Create Metadata Object
Creates a new list element (metadata object) under a specified metadata type (list) in your Datascope account. Use this endpoint to add new items to your Datascope reference lists — such as new products, clients, or other custom list types — from data in external systems.
This endpoint requires the following configuration parameter:
Metadata Type: Enter the name of the metadata list (list type) under which the new element should be created. This corresponds to the metadata_type field in the Datascope API (e.g., products, clients).
The request body should include the following list_object fields for the new element:
name: The display name of the new list element (required).
code: A unique identifier code for the element.
description: A brief description of the element.
attribute1 and attribute2: Optional custom attribute values for additional metadata fields.
Use the List Metadata Objects source endpoint to verify existing metadata types and elements in your Datascope account before creating new ones, to avoid duplicates.
Update Metadata Object
Updates an existing metadata list element in your Datascope account by its numeric ID. Use this endpoint to keep your Datascope reference lists in sync with an authoritative source system when list item details change.
This endpoint requires the following configuration parameter:
Metadata Object ID: Enter the numeric ID of the metadata list element to update. Element IDs can be retrieved using the List Metadata Objects data source endpoint.
The request body fields mirror the Create Metadata Object payload (list_object fields: name, code, description, attribute1, attribute2). Include only the fields that need to be updated.
Create Metadata Type (List)
Creates a new empty metadata list (metadata type) in your Datascope account. Use this endpoint to programmatically provision new reference lists in Datascope, which can then be populated with elements using the Create Metadata Object endpoint.
The request body should include the following fields:
name: The display name of the new list (required).
description: A brief description of the list's purpose.
code: A unique identifier code for the list.
list_type: The type classification of the list, as defined in Datascope.
The API response returns the created list object, including the system-generated numeric ID that can be used to reference this list in subsequent operations.
Update Metadata Type (List)
Updates an existing metadata list (metadata type) in your Datascope account by its numeric ID. Use this endpoint to modify list properties such as the name, description, or code of an existing reference list.
This endpoint requires the following configuration parameter:
Metadata Type ID: Enter the numeric ID of the metadata list (metadata type) to update. List IDs can be retrieved from the Datascope account or by first creating the list using the Create Metadata Type endpoint.
The request body fields mirror the Create Metadata Type payload (name, description, code, list_type).
Bulk Update Metadata Objects
Replaces or upserts multiple metadata list elements in a single API call. Use this endpoint for bulk synchronization scenarios where you need to refresh an entire reference list (such as a product catalogue or client list) from an external system in one operation.
The request body must include the following fields:
metadata_type: The name of the metadata list (list type) to update.
name: The display name of the list.
list_objects: An array of list element objects to upsert. Each element should include: code (unique identifier), name, description, attribute1, and attribute2.
This endpoint replaces or upserts all elements provided in the list_objects array. Use with care in production environments, as it can overwrite existing list data.
The Bulk Update Metadata Objects endpoint is the most efficient way to synchronize large reference lists between an external system and Datascope. For adding or modifying individual elements, use the Create Metadata Object or Update Metadata Object endpoints instead.
Assign Task
Creates a task assignment in Datascope, assigning a specific form to a user for completion at a given location on a specified date. Use this endpoint to automate task dispatching — for example, scheduling inspections or work orders based on data from an external planning or scheduling system.
The request body should include the following fields:
form_id: The numeric ID of the Datascope form to be completed as part of this task.
user_id: The numeric ID of the Datascope user to whom the task is assigned.
date: The date on which the task should be completed, in yyyy-MM-dd format.
Location and contact fields: Location ID or address details for where the task should be performed.
task_instruction (optional): Free-text instructions for the assigned user.
gap (optional): Time gap or interval setting for recurring task scheduling.
code (optional): A custom identifier code for the task assignment.
Ensure that the form_id and user_id values in your Nexset correspond to valid forms and users in your Datascope account. Use the Datascope List Task Assigns source endpoint to verify existing assignments and IDs.
Task assignments created via this endpoint appear immediately in the assigned user's Datascope mobile app task list. Ensure that task dates and form assignments are correct before activating this destination flow.
Datascope destinations can also be manually configured to send data to any valid Datascope External API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
All Datascope External API write endpoints begin with https://www.mydatascope.com/api/external/, use the POST method, and accept JSON (application/json) payloads. For update operations, append the numeric ID of the object to update to the end of the URL. You do not need to add an Authorization header manually—it is applied automatically from your Datascope credential. Most write endpoints accept a single JSON object per request; the Bulk Update Metadata Objects endpoint is the exception, accepting an array of elements in the list_objects field for batch synchronization.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Datascope endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Datascope until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
