---
sidebar_label: Register your scope
toc_max_heading_level: 3
doc_id: 0c7f82d1-c4ec-48e8-a3b7-75cff9cd22f2
description: >-
  Guide for registering a custom scope service in your organization using CLI or
  API commands.
keywords:
  - scope registration
  - CLI
  - API
  - custom scope
  - service configuration
---

import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Register the scope

Once you've defined your scope as a service, you need to register it in your organization so it becomes available for use.

You can do this using the [CLI](/docs/cli/) or the [API](/docs/api/scope-type-create). 

<Tabs
defaultValue="create-scope-type-cli"
values={[
{ label: 'CLI', value: 'create-scope-type-cli' },
{ label: 'cURL', value: 'create-scope-type-curl' },
]}>
    <TabItem value="create-scope-type-cli">
        ```bash
        np scope type create \
          --body '{
            "nrn": "organization=1:account=2:namespace=3",
            "type": "custom",
            "name": "My scope",
            "status": "active",
            "description": "Description of scope",
            "provider_type": "service",
            "provider_id": "5f21c3d8-6b2a-4e3f-9b62-18a7c91e7d3b"   //  the ID of your scope specification
          }'
        ```
    </TabItem>
    <TabItem value="create-scope-type-curl">
        ```bash
        curl -X POST "https://api.nullplatform.com/scope_type" \
             -H "Content-Type: application/json" \
             -d '{
                "nrn": "organization=1:account=2:namespace=3",
                "type": "custom",
                "name": "My scope",
                "status": "active",
                "description": "Description of scope",
                "provider_type": "service",
                "provider_id": "5f21c3d8-6b2a-4e3f-9b62-18a7c91e7d3b"   //  the ID of your scope specification
             }'
        ```
    </TabItem>
</Tabs>

:::note Request details

In this example:

- the scope is available to developers with access to account `2` in your organization `1`.
- it's associated with the scope specification with ID `5f21c3d8-6b2a-4e3f-9b62-18a7c91e7d3b`.
:::