Publish Test


You can publish a test using following API endpoint:

 https://api.hackerearth.com/recruiter/v1/tests/publish/

Authentication

The client authentication is done using your unique client_id and client_secret.

You can refer to your Dashboard settings, for client_id and client_secret under API details.

client_id

Type: String

Description: client_id is a 67 character random key that serves as an identification for a particular client and must be provided when communicating with the API as a parameter to the API endpoint.

Example: d8a20ae8e475209er4b1faa72ede88a174423cc2029c.api.hackerearth.com

client_secret

Type: String

Description: client_secret is a 40 character random key that serves as an identification for a particular client and must be provided when communicating with the API as a parameter to the API endpoint.

Example: 2b0ff29f4f8751487540604cdab5611e6135f41c


Making requests

Test will be publishable only if problems are added and test duration is set.

client_id, client_secret and test_id are the required parameters for making request to this API endpoint.

All the requests to the API must be made using POST request method.

client_id and client_secret are explained above.

test_id

Type: Integer

Description: test_id is an unique integer for your test.
Refer advance settings section under test settings for test_id.

Example: 5841

Sample request using python

#!/usr/bin/env python

import json
import requests

CLIENT_ID = "d8a20ae8e475209e0eb1faa72ede88a174423cc2029c.api.hackerearth.com"
CLIENT_SECRET = "2b0ff29f4f8751487450604cdab5611e6135f41c"
TEST_ID = 53

payload = {
    'client_id': CLIENT_ID,
    'client_secret': CLIENT_SECRET,
    'test_id': TEST_ID
}
r = requests.post("https://api.hackerearth.com/recruiter/v1/tests/publish/", data=json.dumps(payload))
print r.json()

Using cURL

curl --data '{"client_id":"d8a20ae8e475209e0eb1faa72ede88a174423cc2029c.api.hackerearth.com","client_secret":"2b0ff29f4f8751487450604cdab5611e6135f41c","test_id":53}' https://api.hackerearth.com/recruiter/v1/tests/publish/


Response

Response returned will be in JSON format.

Sample response

{
    "message": "Request successful",
    "ecode": [],
    "emessage": [],
    "mcode": "SUCCESS"
}

mcode

Type : String

Description: Message code abbreviated as mcode.

message

Type: String

Description: A message for user regarding the success of request.

message and mcode are related to each other according to the following table:

mcode message
SUCCESS Request successful
FAILED Request failed

ecode

Type: List

Description: Error codes abbreviated as ecode.

emessage

Type: List

Description: A message explaining the error occurred during request processing.

emessage and ecode are related to each other according to the following table:

ecode emessage
AUTHFAILED Authentication Failed
ARGMISSING Request argument missing
TESTNOTFOUND Test not found
ALREADYPUBLISHED Test already published
DURATIONZERO Test duration not set
PROBLEMZERO Test does not have problem set
DATETIMENOTSET Test date time not set
LIMITEXCEEDED Client exceeded its request limit. Please contact support@hackerearth.com.
ACCESSERROR You are not authorized to access this feature. Please contact support@hackerearth.com.


Errors (Mishandled API responses)

If you have provide wrong client_id or client_secret the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
         "AUTHFAILED"
    ],
    "emessage": [
        "Authentication Failed."
    ],
    "mcode": "FAILED"
}

If mandatory POST arguments are not provided, the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "ARGMISSING"
    ],
    "emessage": [
        "Request argument missing: 'test_id'."
    ],
    "mcode": "FAILED"
}

If wrong test_id is provided the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "TESTNOTFOUND"
    ],
    "emessage": [
        "Test not found"
    ],
    "mcode": "FAILED"
}

If user is not authorized to access the test, the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "ACCESSERROR"
    ],
    "emessage": [
        "You are not authorized to access this feature. Please contact support@hackerearth.com."
    ],
    "mcode": "FAILED"
}

If the API request limit has exceeded, the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "LIMITEXCEEDED"
    ],
    "emessage": [
        "Client exceeded its request limit. Please contact support@hackerearth.com."
    ],
    "mcode": "FAILED"
}

If the test is already published, the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "ALREADYPUBLISHED",
    ],
    "emessage": [
        "Test already published",
    ],
    "mcode": "FAILED"
}

If the test duration is not set, then test will not be publishable and the JSON response returned will look like:

{
    "message": "Request failed",
    "ecode": [
        "DURATIONZERO"
    ],
    "emessage": [
        "Test duration not set"
    ],
    "mcode": "FAILED"
}

et cetra. So in these cases please take a look at your test details at Recruiter dashboard.

If any other issue occurred do reach us out at api@hackerearth.com

Notifications
View All Notifications

?