Mirakl Users API

The Users API from Mirakl — 1 operation(s) for users.

Operations 1

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /api/users/shops/roles List shop roles · RO02 - List shop roles #
Ask an LLM
“What user roles are available for a shop?”
“Which roles can I assign to my shop's users?”
Tell an agent
List the roles for shop {shop_id}.
Show the available shop user roles.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/mirakl:mirakl-users-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

mirakl-users-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Mirakl Users API
  version: ''
  description: 'Operations tagged Users across 4 of this provider''s published API definitions: mirakl-mcm-seller-openapi.json, mirakl-mmp-front-openapi.yaml, mirakl-mmp-seller-openapi.json, mirakl-mms-seller-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- description: URL to be replaced by your Mirakl instance URL
  url: https://your-instance.mirakl.net
tags:
- name: Users
paths:
  /api/users/shops/roles:
    get:
      description: 'Call Frequency


        Recommended usage: On each user role view


        Maximum usage: On each user role view


        Read More


        More context'
      operationId: RO02
      parameters:
      - description: Use this parameter when your user has access to several shops. If not specified, the shop_id from your default shop will be used.
        explode: true
        in: query
        name: shop_id
        required: false
        schema:
          type: integer
          format: int64
        style: form
      responses:
        '200':
          content:
            application/json:
              examples:
                application/json-0:
                  summary: Example with business values (application/json)
                  value:
                    roles:
                    - code: GROUP_SHOP_ADMIN
                      description: Access to "Dashboard Statistics", access to the "Settings", "Information", and "User Management" menus, ability to call Shop API.
                    - code: GROUP_SHOP_ACCOUNTANCY
                      description: Access to "Statements" and "Transaction History".
                    - code: GROUP_SHOP_INVENTORY
                      description: Access to "Inventory" dashboard, management and messages, and "Mapping Configuration".
                    - code: GROUP_SHOP_SALES
                      description: Access to "Message", "Order" and "Revenue" dashboards, and "Order Management".
                    - code: GROUP_SHOP_SUPPORT
                      description: Access to "Message" and "Order" dashboards, ability to upload order documents and edit seller order references.
                application/json-auto:
                  summary: Complete example with value types (application/json)
                  value:
                    roles:
                    - code: string
                      description: string
              schema:
                type: object
                $ref: '#/components/schemas/RO02_Response_200'
          description: OK
      security:
      - Shop-API-Key:
        - ROLE_PARTNER_SHOP_USER_CREATE
        - ROLE_SHOP_ADMIN
      summary: RO02 - List shop roles
      tags:
      - Users
    servers:
    - description: URL to be replaced by your Mirakl instance URL
      url: https://your-instance.mirakl.net
components:
  schemas:
    RO02_Response_200:
      type: object
      properties:
        roles:
          type: array
          items:
            $ref: '#/components/schemas/RO02_Response_200_Roles'
    RO02_Response_200_Roles:
      type: object
      properties:
        code:
          type: string
        description:
          type: string
  securitySchemes:
    Shop-API-Key:
      in: header
      name: Authorization
      type: apiKey
      x-authorization: '{{SHOP_KEY}}'
    Front-Bearer-Token:
      bearerFormat: JWT
      scheme: bearer
      type: http
      x-authorization: '{{FRONT_BEARER_TOKEN}}'
    OAuth-2:
      description: For more information, see our [Authentication System documentation](https://help.mirakl.com/docs/customers/page/topics/Mirakl/partners_integration/authentication_system.htm)
      flows:
        authorizationCode:
          authorizationUrl: https://auth.mirakl.net/authorize
          refreshUrl: https://auth.mirakl.net/oauth/token
          scopes: {}
          tokenUrl: https://auth.mirakl.net/oauth/token
      type: oauth2
    shop_api_key:
      in: header
      name: Authorization
      type: apiKey
      x-authorization: '{{SHOP_KEY}}'
x-refined-from:
- mirakl-mcm-seller-openapi.json
- mirakl-mmp-front-openapi.yaml
- mirakl-mmp-seller-openapi.json
- mirakl-mms-seller-openapi.json
x-group-parameters: true