api dox

sean

aa11 Ok, looking into this.

The lack of an error message is by design - there doesn't seem to be any problem with your code, but if you look at r.status_code and r.text you'll see that there was a server-side error.

aa11

sean but if you look at r.status_code and r.text you'll see that there was a server-side error.

I added the following at the end:

print (r.status_code)
print (r.text)

And then when run, yes, I see a 400:

400
{"detail":"JSON parse error - Expecting value: line 1 column 1 (char 0)"}

sean

aa11 I've updated the original example to use json= instead of data= in the API call.

If you use that example with [] as your destinations and valid addresses in the source and forwards then it should work.

Note that all of the addresses must have valid domain names so if you're actually trying to use "MY_DOMAIN.com" that won't work (since underscores aren't allowed in domain names).

aa11

sean I've updated the original example to use json= instead of data= in the API call.

That did it!

I saw cornelius use data=json.dumps() but couldn't get that to work either. Switching from data= to json= did the trick.

Also, having that debugging output (viar.status_code and r.text) is helpful.

Note that all of the addresses must have valid domain names so if you're actually trying to use "MY_DOMAIN.com" that won't work (since underscores aren't allowed in domain names).

Of course. But good thing to mention.

Thanks!!

sean

For those of you playing along at home, we've recently pushed an update that changed the various API endpoints for mail users from /mail/user to /mailuser.

The generated API refs will be updated soon.

gelu

Hah! The tool I used to allow my users to change their mailbox passwords after migration from WF was crashing the other day. I tracked down the changes and fixed my code.

The people at Opalstack are really helpful and crazy fast at responding to issues raised both here or through tickets. It would be helpful though if we had some mailing list or RSS feed to keep updated with both changes and new stuff at Opalstack (maybe I don't know about it...). It would a lot of time for both chasing and error introduced by a changes like this and to the good people at Opalstack who answer our questions.

sean

gelu We're not officially publishing changes to the API because the API itself has not been officially released.

Once we've finalized the API and have fully documented everything, then we'll start managing changes publicly.

gelu

sean That's reasonable. What I was suggesting was not necessarily related to the API itself, but rather about building a channel of communication so that we know what's coming and when. This would be for the actual Opalstack users and would preferably lean on the technical side. I can read the blog about new and exiting stuff and I can check the boards for solutions. This channel would serve an entirely different purpose, if it makes sense to you, of course.

sean

gelu We'll most likely use this community forum as the primary channel for communicating updates like that.

RSS feeds are already available here: https://community.opalstack.com/d/5-forum-rss-feeds 🙂

dcd

API working great -- going to save my skin doing 100's of email account migrations -- thanks!

Having trouble with api/v0/mailuser/pwdch/ --> 400 Bad Request {"error": "INVALID"}
Here's my code:

    r = requests.post(
        'https://my.opalstack.com/api/v0/mailuser/pwdch/',
        auth=TokenAuth(TOKEN),
        json={
             'id': 'd035b2b7-c55b-413b-a5f1-4edbe7ea5de0', 
             'password': 'some password'
           },
   )
  print (r.status_code, r.reason, r.text)
  > 400 Bad Request {"error": "INVALID"}

No problem with other requests.
I have tried all combinations of data= vs. json= and json.dumps() vs. normal dict
Any ideas what I'm doing dumb here appreciated.

sean

dcd pwdch takes a list, try this:

    r = requests.post(
        'https://my.opalstack.com/api/v0/mailuser/pwdch/',
        auth=TokenAuth(TOKEN),
        json=[{
             'id': 'd035b2b7-c55b-413b-a5f1-4edbe7ea5de0', 
             'password': 'some password'
           }],
   )

dcd

sean Damn. No Dice Sean. Here's a complete session with just a few details redacted, hopefully give a clue what dumb-ass thing I am doing...

mailbox_id = 'd035b2b7-c55b-413b-a5f1-4edbe7ea5de0'
... r = requests.get(
...     'https://my.opalstack.com/api/v0/mailuser/read/{}'.format(mailbox_id),
...     auth = TokenAuth(TOKEN),
... )
... print(r, r.content)
... 
<Response [200]> b'{"id": "d035b2b7-c55b-413b-a5f1-4edbe7ea5de0", "name": "<xxx>", "pending_deletion": false, "ready": true, "imap_server": "<uuid>", "init_created": true}'
r = requests.post(
...     'https://my.opalstack.com/api/v0/mailuser/pwdch/',
...     auth=TokenAuth(TOKEN),
...     json=[{
...         'id'      : mailbox_id,
...         'password': 'some password'
...     }],
... )
... print(r, r.reason)
... 
<Response [400]> Bad Request

dcd

dcd I think I got it. My passwords arer long and random, but did not contain any upper-case letter.
Saw a tip on another thread to watch XHR requests while doing operations via control panel -- excellent tip, that gave me the answers I needed. Thanks Sean, sorry for the diversion.

dcd

dcd Proof in the pudding:

... r = requests.post(
...     'https://my.opalstack.com/api/v0/mailuser/pwdch/',
...     auth=TokenAuth(TOKEN),
...     json=[{
...         'id'      : mailbox_id,
...         'password': 's0me P@ssword'
...     }],
... )
... print(r, r.reason)
... 
<Response [200]> OK

sean

as of June 2021 the API is at v1. The new docs are:

https://my.opalstack.com/api/v1/doc/
https://my.opalstack.com/api/v1/redoc/

allyn

Any chance you can add to the docs where lists are required? Got caught with DNSRecord/Update failing in my ddns script due to not passing a list. I know you have mentioned that lists are now required at a number of end points, would be great if those can be called out in the V1 docs. Thanks!

sean

allyn I believe all create endpoints require lists now.

« Previous Page