What's wrong with this REST API POST member call?

Jeff Wogan

I'm trying to create a member through the CS REST API call and all I'm getting back are "Bad Request" responses. I know the ticket is good. I've tried using ...api/v2/... , different group_ids, different Content-Types. What am I missing? Thanks for any help.

I'm sending:

POST http://{llserver}/livelink/llisapi.dll/api/v1/member HTTP/1.1

Host: {llserver}

Connection: keep-alive

Content-Length: 32

Cache-Control: no-cache

Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop

Content-Type: application/x-www-form-urlencoded

User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

OTCSTICKET: CR7ihwDGmWQvtbLNpGhtCD0I6IIen682IzvFtAmG2kZEiCqQckk4VVEb1aJXIyfI+dFSKeptmFTAROYI1M2LVw==

Postman-Token: efbff9d3-670f-951b-2da3-9e52b627b7c2

Accept: /

Accept-Encoding: gzip, deflate

Accept-Language: en-US,en;q=0.8

Cookie: LLTZCookie=0

type=0&name=newTestMember&group_id=2015

And I get back:

HTTP/1.1 400 400 Bad Request

Cache-Control: no-cache, no-store, must-revalidate, max-age=0

Pragma: no-cache

Content-Type: text/html

Expires: 0

Server: Microsoft-IIS/7.5

Access-Control-Allow-Origin: chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop

Access-Control-Allow-Headers: OTCSTicket, OTDSTicket, MYSAPSSO2, Authorization, Content-Type, Content-Length

Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS

Access-Control-Expose-Headers: OTCSTicket, Content-Type

Access-Control-Max-Age: 86400

OTCSTicket: CR7ihwDGmWQvtbLNpGhtCD0I6IIen682IzvFtAmG2kbiudzlNDscrtElI4nWgufsVXL+ThfuGrdf5nUKBDmoGg==

Status: 400 Bad Request

X-Powered-By: ASP.NET

Date: Thu, 11 Aug 2016 12:59:23 GMT

Content-Length: 11

Bad Request