Skip to main content
GET
/
v1
/
jobs
/
{jobId}
/
applications
/
{applicationId}
/
score
cURL
curl --request GET \
  --url https://embed.nova.dweet.com/v1/jobs/{jobId}/applications/{applicationId}/score \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Tenant-Id: <x-tenant-id>'
{
"scoringJobId": "sj_abc123def456",
"status": "completed",
"jobId": "job-123",
"applicationId": "app-456",
"result": {
"score": 7,
"assessment": {
"verdict": "Strong candidate with solid backend experience.",
"strengths": [
"6 years of backend engineering experience"
],
"concerns": [
"No direct Kubernetes experience"
],
"interviewFocus": [
"Probe depth of distributed systems knowledge"
]
}
},
"completedAt": "2025-01-15T10:30:45Z"
}
Retrieve score results using your own application ID. Useful when you don’t have Nova’s scoringJobId.

When to Use

  • You only stored your applicationId, not the scoringJobId
  • Building a lookup feature in your UI
  • Debugging or auditing past scores

Response

Returns the same response format as Get Score by Scoring Job ID:
StatusDescription
queuedJob is waiting to be processed
processingJob is currently being scored
completedScoring finished successfully
failedScoring could not be completed

Re-scored Applications

If the application has been re-scored multiple times (using rescore: true), this endpoint returns the most recent score.
To access historical scores, use the specific scoringJobId from each scoring job.

Example

const jobId = 'job-123';
const applicationId = 'app-456';

const response = await fetch(
  `https://embed.nova.dweet.com/v1/jobs/${jobId}/applications/${applicationId}/score`,
  {
    headers: {
      'Authorization': `Bearer ${apiKey}`,
      'X-Tenant-Id': tenantId,
    },
  }
);

const result = await response.json();

if (result.status === 'completed') {
  console.log(`Score: ${result.result.score}`);
  console.log(`Verdict: ${result.result.assessment.verdict}`);
}

Alternative

If you have Nova’s scoring job ID, use Get Score by Scoring Job ID for direct lookup.

Authorizations

Authorization
string
header
required

API key authentication. Use your environment-specific API key (sk_test_* for sandbox, sk_live_* for production).

Headers

X-Tenant-Id
string
required

Your customer/tenant identifier. Used for data isolation and per-customer metrics. Tenants are created automatically on first request.

Path Parameters

jobId
string
required

Your job ID

applicationId
string
required

Your application ID

Response

Score result retrieved

scoringJobId
string
required
status
enum<string>
required
Available options:
queued,
processing,
completed,
failed
jobId
string
required
applicationId
string
required
result
object
error
object
queuedAt
string<date-time>
completedAt
string<date-time>
failedAt
string<date-time>