---
updatedAt: 2025-09-08T14:36:27.000Z
agentTools:
  projectIndex: https://developer.operations1.com/llms.txt
---

# Test API functions

How can I test my access to the API and call functione

# Test directly through the developer portal

You can call API functions from within our developer portal. This requires always the following information:

* A valid API token set up
* The "tenant", which is your Operations1 instance, which is part of the URL: https\://**tenant**.operations1.app
* The API version you want to call, either a specific one or the latest

Open the developer portal and navigate to the function you want to test and fill the required parameters. For example the "[Get a user](https://developer.operations1.com/reference/getuserbyid)" function:

<Image align="center" src="https://files.readme.io/1732485983bb4a47f44e652206824482076badb202dee6acfa2b433e4f5ffff7-req_info.png" />

Each function may require additional parameters, like the "userId" in this example. After filling those you can hit "Try It!" to see immediately the result:

<Image align="center" className="border" border={true} src="https://files.readme.io/885d34b2a36e4527cb2506f9562f5b79aead4d5bb76860934a4bd333e78dd2f1-test_api.png" />

You get immediately the result. This way all API calls can be tested without any addtional coding.

# Use the API in various environments

Besides the direct test you can copy the necessary code for an API call on the same page. Select the language and then copy the code snippet into the environment of your choice:

<Image align="center" className="border" border={true} src="https://files.readme.io/8556f081b3f3a07d0da04eb5df8335e6a85b19f1ba784973e2fd7322c031af84-lang.png" />

In our recipe section you can find code examples for different use-cases: <https://developer.operations1.com/recipes>

## Other tools

There are many different ways, how the Operations1 API can be called to integrate with other systems to im- and export data to the Platform. Any system, which can do REST-API calls can be used to automate processes.

### Power Automate/LogicApp

Many users use for example Microsoft PowerAutomate/LogicApps to configure automation flows within their O365/Azure environment. Calling the same "Get a user" function could be achieved with a HTTP block:

<Image align="center" src="https://files.readme.io/fd84c7d4294708c039756855e189eb029c5b5b4feb1c78d675e03d92aaf1d48b-logicapp.png" />

### Postman

There are other tools to work with APIs such as [Postman](https://www.postman.com/), where you can automate things, keep variables and maintain collections for more detailed testing. For example preserve the authentication:

<Image align="center" className="border" border={true} src="https://files.readme.io/c4b40fcdba3e604a08cef000e8d7ce6264b005b3b325b86942792d7816de4761-postman-1.png" />

Provide specific data as vaiables:

<Image align="center" className="border" border={true} src="https://files.readme.io/e435f63d921d051170a7f33d28823355826b0daf541335a89cea5a5b51a0b036-postman-2.png" />

Calling the "Get a user" function could look like this:

<Image align="center" className="border" border={true} src="https://files.readme.io/7e1ace7a141990dfac5802fdea90e69568a00d68afdc5bd28a5c6fe4547192d0-postman-3.png" />

## Return values

Results returned from the API functions are provided as JSON payload, no matter with which method you call them. For the "Get a user" function this would look like this:

```json
{
    "id": 2725,
    "name": "a.admin",
    "archived": false,
    "externalId": null,
    "displayName": "a.admin",
    "firstName": "Alex",
    "lastName": "Admin",
    "email": "alex.admin@operations1.com",
    "job": null,
    "defaultLocale": null,
    "role": {
        "id": 11,
        "name": "Admin"
    }
}
```