http.asc #1

=== Authentication Methods

[[post_auth_v1_login]]
==== `POST /auth/v1/login`

Generates the Perforce login token for the server.

===== Request Headers

[cols="2*", options="header"]
|===
| Header Name
| Notes

| `Accept`
| `application/json`, `text/plain`

| `Content-Type`
| `application/json`

| `X-Perforce-Helix_Web_Services-*`
| See <<per_request_configuration>>
|===

===== Request Body JSON

A single JSON object with the following keys

[cols="2*", options="header"]
|===
| Property
| Description

| `user`
| The Helix Versioning Engine login

| `password`
| The password for the particular user
|===

===== Response Headers

[cols="2*", options="header"]
|===
| Header Name
| Notes

| `Content-Type`
| `application/json`, `text/plain`
|===

===== Response Body

See <<error_responses>> for the format of failures.

Upon success, when `Content-Type` is `text/plain`, the response body is simply the P4 ticket value.

....
16A76F005802E742E834163A22A4DED4
....

When `Content-Type` is `application/json`, the response is a JSON object.

[source,json]
----
{
  "ticket": "16A76F005802E742E834163A22A4DED4"
}
----