User defined API

0

Hi Nikolaus,
I've checked how it works in our environment (version 2025.2.1.35).

First of all i've created test api definition as seen in screenshots, a simple example - just starting new empty workflow.
An important thing was to check Authorization mode, documented here (without it i've been getting permission errors):
* https://docs.webcon.com/docs/2025R2/Studio/Process/APIDefinition#5-authentication-mode

Second part is the API client/secret - I'm using a full access token for development purposes, but to test the scopes i'm specyfing those in authorization requests.
Make sure, that you've saved those scopes allowed per specific application, so you are trying to get permissions to scope, to which you can get those.

Now testing, using curl it goes like that:

1. We log in as the application:
curl -X 'POST' \
'https://webcondevelopment/api/oauth2/token' \
-H 'accept: application/json' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'grant_type=client_credentials&client_id={your_client_here}&client_secret={your_secret_here}&scope=App.UserDefAPI.ReadWrite.All'

2. Using returned access_token we can now try to execute the action:
curl -X 'POST' \
'https://webcondevelopment/api/udef/db/1/test' \
-H 'accept: application/json' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {access_token}' \
-d '{}'

From permission perspecitve I gave permissions on the application level and on process level.

When error says Invalid scopes i would check 3 times if those are properly defined on both ends - webcon, and the application/script executing the api call, it looks like it's the first thing that webcon checks before it proceeds to do anything else.