REST API: 403 Client Error: Forbidden for url after Create Request using Token

Note that that endpoint will return a token even if the request itself is invalid, or the credentials are invalid.  My assumption is that there's something wrong with that initial request.  There may also be something wrong with the second request, but the 403 needs to be fixed first.

Can you give some example of what you're doing to get the token?

Note that that endpoint will return a token even if the request itself is invalid, or the credentials are invalid.  My assumption is that there's something wrong with that initial request.  There may also be something wrong with the second request, but the 403 needs to be fixed first.

Can you give some example of what you're doing to get the token?

Hey Craig, Thank you for the quick response. I think the initial request should be fine in regards to the credentials and the endpoint, because if I use the same credentials in the header for the create request, everything works fine. 

Can you show me the structure of that, though?  Does it include the vault guid and things?

Sorry for the late answer:

The headers look like this: 

I'm save the token like this: token = result.get("Value")

Show the actual content of the request to the authentication endpoint.  That structure is probably wrong, which is why the token is invalid.

Here is the actual content of the authentication request:

postman request POST 'ecb.enerprice.ch/.../authenticationtokens.aspx' \
--header 'Content-Type: application/json' \
--header 'Cookie: ASP.NET_SessionId=gnqbp50l2zpu0dhnzpf4z5wd; token=ag7bf6XOdtr9zE9_kgY_0WsijVgjNXGqD60Bt4wkgtt7bD3ZqbNx2dHuu1IegJqXdxknBx-gBf-_nhKpaelrMLoZzuIgcXcUT5p_WQNfIWIjyA402QnqwK0iDa0ZiSp3JW5JhRCi3tIt7jkZzh2uvHmR552EDccwZPbWZZzZtak6jW88nPOEUZK5-WrEopZz5hLDcZxdOHG-V8cKi8Xrn6GiXyBTC6vuO3C4EPkW2dqiYWD2rJcHQOQF6OhBfhgU-4TS3s-NaXt-UBk0RrSeEa454GMvnVmmA6SlwT4uAsMmWMiDejKCRyBJmAqn-b9PefevFh9JATiokJS-5Gi1zw' \
--body '{
"Username": "myUser",
"Password": "myPassword",
"VaultGuid": "{216DA69D-4595-408E-AD27-E98EDD13759A}"
}'

Looks reasonable; only thing I can see vs our postman collection (MFilesSamplesAndLibraries/Libraries/Postman/M-Files.postman_collection.json at master · M-Files/MFilesSamplesAndLibraries) is that the vault GUID there is listed without braces. 

I removed the braces but I still get the same error... Thank you very much for providing the postman collection. This will probably help me a lot in the future!

I'm trying to update a property on an object. I followed the example in postman collection and I struggle here as well... Let me know If I should create a new question:

postman request POST 'ecb.enerprice.ch/.../3056' \
--header 'Content-Type: application/json' \
--header 'X-Username: user' \
--header 'X-Password: passsword' \
--header 'X-Vault: 216DA69D-4595-408E-AD27-E98EDD13759A' \
--header 'Cookie: ASP.NET_SessionId=y2yejhtbthwvcspynu15g5c4; token=ag7bf6XOdtr9zE9_kgY_0WsijVgjNXGqD60Bt4wkgtt7bD3ZqbNx2dHuu1IegJqXdxknBx-gBf-_nhKpaelrMLoZzuIgcXcUT5p_WQNfIWIjyA402QnqwK0iDa0ZiSp3JW5JhRCi3tIt7jkZzh2uvHmR552EDccwZPbWZZzZtak6jW88nPOEUZK5-WrEopZz5hLDcZxdOHG-V8cKi8Xrn6GiXyBTC6vuO3C4EPkW2dqiYWD2rJcHQOQF6OhBfhgU-4TS3s-NaXt-UBk0RrSeEa454GMvnVmmA6SlwT4uAsMmWMiDejKCRyBJmAqn-b9PefevFh9JATiokJS-5Gi1zw' \
--body '[{
"PropertyDef": 3056,
"TypedValue": {
"DataType": 1,
"Value": 1234567890
}
}]'

I get this error:

Did you mean to do a put?

https://developer.m-files.com/APIs/REST-API/Reference/resources/objects/type/objectid/version/properties/id/