Magento API

Magento GraphQL API provides comprehensive e-commerce data access capabilities, enabling businesses to retrieve product catalogs, customer information, order data, and inventory details through flexible GraphQL queries for seamless integration with modern e-commerce workflows.

Power end-to-end data operations for your Magento API API with Nexla. Our bi-directional Magento API connector is purpose-built for Magento API, 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 Magento API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Magento API 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

Prerequisites

Before creating a Magento API credential, you need to identify your Magento server URL and optionally obtain an authorization token if you need to access protected data. The authorization token is optional for accessing public data, but required for accessing protected resources like customer data, orders, and inventory information.

To obtain your authorization token (if needed for protected data), follow these steps:

1. Sign in to your Magento admin panel using your administrator credentials.

2. Navigate to System > Integrations in the Magento admin menu.

3. Click Add New Integration to create a new integration.

4. Enter a name for the integration (e.g., "Nexla Integration") in the Name field.

5. Enter your email address in the Your Email field.

6. Enter a password in the Your Password field to secure the integration.

7. In the API tab, select the resource access permissions you need for your integration. You can choose specific resources or select All for full access.

8. Click Save to create the integration.

9. Click Activate to activate the integration and generate the access token.

10. After activation, the Access Token will be displayed. Copy this token immediately, as it may not be accessible again after you navigate away from the page.

11. Store the authorization token securely, as you will need it to configure your Nexla credential. The authorization token provides access to your Magento data based on the permissions you configured, so treat it as sensitive information.

The authorization token is sent in the Authorization header with the Bearer prefix (e.g., Authorization: Bearer {token}) for all API requests to the Magento GraphQL API. The token authenticates your integration and grants access to Magento resources based on the permissions configured for the integration. If you only need to access public data (such as public product catalogs), you can leave the authorization token blank. For detailed information about authorization tokens, API authentication, and available GraphQL queries, refer to the Magento GraphQL API documentation and Magento authorization tokens documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Magento Server	Yes	No	Your magento host url. Ex: http://<magento2-server>
Authorization Token	No	Yes	Admin authorization token for accessing protected data. Leave blank if you only want to access public data.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Magento API

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

Magento uses token-based authentication for accessing protected data through the GraphQL API. The authorization token is sent in the Authorization header with the Bearer prefix to authenticate API requests to the Magento GraphQL API.

3. Enter your Magento server URL in the Magento Server field. This should be the base URL of your Magento instance (e.g., https://yourstore.com or http://localhost/magento2). The server URL is used to construct GraphQL API endpoint URLs. Ensure the URL includes the protocol (http:// or https://) and does not include a trailing slash.

4. Enter your Magento authorization token in the Authorization Token field (optional). This is the access token you obtained from your Magento admin panel (System > Integrations). The authorization token is sent in the Authorization header with the Bearer prefix for all API requests to the Magento GraphQL API. Leave this field blank if you only need to access public data that doesn't require authentication. The authorization token is sensitive information and must be kept confidential if provided.

   The authorization token is optional and only required if you need to access protected data such as customer information, orders, or inventory details. If you only need to access public product catalogs or other public data, you can leave the authorization token field blank. If your authorization token is compromised, you should immediately revoke it in your Magento admin panel (System > Integrations) and create a new integration. Your Magento authorization token can be found in your Magento admin panel (System > Integrations) after creating and activating an integration. The authorization token is sent in the Authorization: Bearer {token} header for all API requests to the Magento GraphQL API. The token provides access to Magento resources based on the permissions configured for the integration. For detailed information about obtaining and managing authorization tokens, API authentication, and available GraphQL queries, see the Magento GraphQL API documentation and Magento authorization tokens documentation.

5. 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.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Magento API connector tile, then select the credential that will be used to connect to the Magento instance, and click Next; or, create a new Magento API credential for use in this flow.

In Nexla, Magento API data sources can be created using pre-built endpoint templates, which expedite source setup for common Magento GraphQL queries. Each template is designed specifically for the corresponding Magento GraphQL query type, making source configuration easy and efficient.
• To configure this source using a template, follow the instructions in Configure Using a Template.

Magento API sources can also be configured manually, allowing you to execute custom GraphQL queries not included in the pre-built templates or apply further customizations to exactly suit your needs.
• To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure data sources to execute common Magento GraphQL queries. Each template is designed specifically for the corresponding Magento GraphQL query type, making data source setup easy and efficient.

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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

Query One Page of Data

This endpoint template executes a GraphQL query that fetches a single page of data from your Magento instance. Use this template when you need to retrieve a fixed set of data that doesn't require pagination, such as category information, product details for a specific SKU, or customer information for a specific ID.

• Enter your GraphQL query in the Query field. This should be a valid Magento GraphQL query that retrieves the data you need. The query should follow Magento GraphQL syntax and reference the appropriate Magento schema fields. For example, to retrieve categories, use: { categories { items { id name } } }. The query is sent as a POST request to the Magento GraphQL endpoint (/graphql) with the query in the request body.
• Enter the JSONPath expression in the JSONPath to Data in Response field to specify which part of the API response should be treated as the relevant data by Nexla. This JSONPath expression should point to the array of items in the GraphQL response. For example, if your query returns categories, use $.data.categories.items[*] to extract all category items from the response. The JSONPath expression determines which data will be extracted and processed by Nexla.

This template is designed for queries that return a single page of results. If your query returns paginated data, use the "Query Paginated Data" template instead. The GraphQL query must be valid according to the Magento GraphQL schema. You can reference the Magento GraphQL queries documentation for available queries and schema information.

The JSONPath expression must correctly reference the structure of your GraphQL response. GraphQL responses typically have a data property containing the query results. Ensure your JSONPath expression matches the structure returned by your specific query.

Query Paginated Data

This endpoint template executes a GraphQL query that fetches multiple pages of data from your Magento instance using pagination. Use this template when you need to retrieve large datasets that span multiple pages, such as all products, all orders, or all customers. The template automatically handles pagination by incrementing the page number for subsequent requests.

• Enter your GraphQL query in the Query field. This should be a valid Magento GraphQL query that includes pagination variables. The query must include variables for page number and page size that will be used for pagination. For example, to retrieve paginated products, use: query Products ($currentPage: Int $pageSize: Int){ products(filter:{} pageSize: $pageSize, currentPage: $currentPage){ items{ id name sku } total_count page_info {page_size current_page total_pages}}}. The query is sent as a POST request to the Magento GraphQL endpoint (/graphql) with the query and variables in the request body.
• Enter the JSONPath expression in the JSONPath to Data in Response field to specify which part of the API response should be treated as the relevant data by Nexla. This JSONPath expression should point to the array of items in the GraphQL response. For example, if your query returns products, use $.data.products.items[*] to extract all product items from the response. The JSONPath expression determines which data will be extracted and processed by Nexla for each page.
• Enter the variable name for the page number in the Query Variable for Page Number field. This should match the variable name used in your GraphQL query for pagination. For example, if your query uses $currentPage, enter currentPage in this field. Nexla will automatically increment this value to fetch subsequent pages of data.
• Enter the starting page number in the Start from Page Number field. This is the initial page number that Nexla will use when fetching data. Typically, this should be set to 1 to start from the first page. Nexla will automatically increment this value for subsequent pages.
• Enter the variable name for the page size in the Query Variable for Page Size field. This should match the variable name used in your GraphQL query for specifying the number of items per page. For example, if your query uses $pageSize, enter pageSize in this field.
• Enter the number of items to fetch per page in the Number of items per page field. This determines how many items will be retrieved in each API request. A larger page size reduces the number of API calls but may increase response time. A smaller page size increases the number of API calls but may improve response time. Choose a value that balances performance with API rate limits.

This template automatically handles pagination by incrementing the page number for each subsequent request. Ensure your GraphQL query includes pagination variables and that the variable names match the values you enter in the configuration fields. The query must return pagination metadata (such as total_count and page_info) to enable proper pagination handling.

The GraphQL query must be valid according to the Magento GraphQL schema and must include pagination variables. You can reference the Magento GraphQL queries documentation for available queries and schema information. The JSONPath expression must correctly reference the structure of your GraphQL response, typically pointing to the items array within the data property.

Consider your API rate limits when setting the page size. Larger page sizes reduce the number of API calls but may take longer to process. Smaller page sizes increase the number of API calls but may be more responsive. Monitor your API usage to optimize the page size for your specific use case.

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.

Configure Manually

Magento API data sources can be manually configured to execute custom GraphQL queries not covered by pre-built templates. Manual configuration provides maximum flexibility for accessing custom queries or when you need advanced GraphQL query configurations.

With manual configuration, you can also create more complex Magento API sources, such as sources that use multiple GraphQL queries or sources that require custom variables or fragments.

API Method

1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the Magento GraphQL API from the Method pulldown menu. Magento GraphQL API uses POST method for all queries, as GraphQL queries are sent in the request body.

API Endpoint URL

3. Enter the URL of the Magento GraphQL API endpoint in the Set API URL field. This should be the complete URL to your Magento GraphQL endpoint, typically {magento_server_url}/graphql where {magento_server_url} is your Magento server URL configured in the credential (e.g., https://yourstore.com/graphql).

Ensure the API endpoint URL is correct and accessible with your current credentials. The Magento GraphQL endpoint is typically located at /graphql relative to your Magento server URL. You can test the endpoint using the Test button after configuring the URL.

Request Body

4. Configure the request body that will be sent to the Magento GraphQL API. The request body should contain your GraphQL query in JSON format. The request body format is: {"query": "{ your_graphql_query }"} for simple queries, or {"query": "{ your_graphql_query }", "variables": { "variable_name": "variable_value" }} for queries with variables.

The request body must be valid JSON and must include a query property containing your GraphQL query. If your query uses variables, include a variables property with the variable values. The GraphQL query must be valid according to the Magento GraphQL schema. You can reference the Magento GraphQL queries documentation for available queries and schema information.

Response Data Path

5. Enter the JSONPath expression in the Response Data Path field to specify which part of the API response should be treated as the relevant data by Nexla. This JSONPath expression should point to the array of items in the GraphQL response. For example, if your query returns products, use $.data.products.items[*] to extract all product items from the response.

The JSONPath expression must correctly reference the structure of your GraphQL response. GraphQL responses typically have a data property containing the query results. Ensure your JSONPath expression matches the structure returned by your specific query. The JSONPath expression determines which data will be extracted and processed by Nexla.

Pagination (if applicable)

6. If your GraphQL query supports pagination, configure the pagination settings in the Pagination section. Select the pagination type that matches your Magento GraphQL query's pagination mechanism. Magento GraphQL typically uses page-based pagination with variables for currentPage and pageSize.

7. Configure the pagination parameters based on your selected pagination type. For page-based pagination, specify the page number parameter name, starting page number, page size parameter name, and page size value.

Save the Data Source

8. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.