Re: REST request to Vertex Cloud

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Including the full debug log would be helpful...(censoring the stuff that's
secret of course)

But at minimum, show

Protocol Used: TLS Version 1.2
http_persist_req(POST) entered.
http_long_ParseURL(): entered
http_long_ParseURL(): entered
do_oper(POST): entered
There are 1 cookies in the cache
cookie=PF not sent (wrong path or domain)
POST /api/inventory/ HTTP/1.1
Host: xxxxxxxxxxxxxxxxxxxxx
User-Agent: http-api/1.39
Content-Type: application/json
Content-Length: 2404
Accept: application/json
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxx
X-Entity-Id: xxxxxxxxxxxxxxxx

senddoc(): entered
{     "customFieldV

recvresp(): entered
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8
Date: Tue, 05 Mar 2019 18:41:22 GMT
Server: nginx/1.12.1
Content-Length: 64
Connection: keep-alive


SetError() #13: HTTP/1.1 400 Bad Request
recvresp(): end with 400
recvdoc parms: identity 64
header_load_cookies() entered
recvdoc(): entered
SetError() #0:
recvdoc(): Receiving 64 bytes.
{"errors":[{"message":"Invalid custom fields specified: [20]"}]}


I suspect that your Content-Type and Accept headers aren't what's
expected...

As Scott mentions, x-www-form-urlencoded doesn't make sense for a actual
REST service

Charles



On Wed, Apr 3, 2019 at 9:28 AM Hudson, Ron <RonHudson@xxxxxxxxx> wrote:

> Has anyone had success using a REST request to the Vertex Cloud for sales
> tax calculations?  If so, any advice?  Vertex has been of little help, all
> their IBM i connections are SOAP.
>
> I'm attempting to use Scott's HTTPAPI version 1.39, O/S version V7R3M0.
>
> The debug log shows I am making the connection, but I am receiving either
> 400 Bad Request or 415 Unsupported Media Type , depending on what
> "Content-Type" is sent.
> Testing the connection with Postman is successful.
>
> Entire test program below:
>
> http_debug(*on: '/tmp/debug.txt');
>
> JSONsecurity = '+
>       {"client_id":"Rest-API-xxxxxxxxxxxxxxxxx",+
>        "client_secret":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",+
>        "username":"xxxxxxxxxxxxxx",+
>        "password":"xxxxxxxxxx",+
>        "scope":"calc-rest-api",+
>        "grant_type":"password"}';
>
> URL = 'https://auth.vertexsmb.com/identity/connect/token';
>
> monitor;
>    resp= http_string('POST': url : JSONsecurity : 'x-www-form-urlencoded');
> on-error;
>    httpcode = http_error();
> endmon;
> *inlr = *on;
>
>
> Results from different "Content-Type" below
> // 'x-www-form-urlencoded'   400 Bad Request                        (this
> was successful in Postman)
>  // 'application/json'                  415 Unsupported Media Type
>  // 'accept: text/json'                 400 Bad Request
>  // 'text/json'                                415 Unsupported Media Type
>  // 'text/plain'                              415 Unsupported Media Type
>  // 'accept: text/plain'                400 Bad Request
>
> Thanks
> Ron
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com