Schema Dictionary
The following list shows the supported fields in the SDEP schema and their corresponding description
Interactive Schema
We use Graphql for our API design, as such, you can view our live schema docs directly from Apollo playground. Just open the playground and add the SDEP staging URL.
Data Fields and Types Comment
User
User can refer to job Applicant, Employer or Admin
id:
IDUNIQ; Each user must have a unique identifierfirstName:
Stringuser first namelastName:
Stringuser last nameavatarUrl:
Stringurl to user avataremail:
Stringuser emailcompanyName:
Stringuser company of workcreatedAt:
DateupdatedAt:
Dateverified:
Booleanif the user account is verified or notrole:
Roleenum which could be applicant, employer, adminplan:
Planenum which could be free, basic or procountry:
StringUser country
Org
Org are the different organisations that an employer can belong to
id:
IDUNIQ; Each org must have a unique identifierorgName:
String!Organisation nameaddress:
String!Organisation addressorgWebsite:
String!Organisation websitecreatedAt:
Datedate created on the platformupdatedAt:
Datedate updated on the platform
Company
Employer's Company details. i.e The company for which the employee works.
id:
IDUNIQ; Each company must have a unique identifiercompanyName:
String!The name of the companyofficeLogoUrl:
StringThe URL to the office logo saved in a storageofficePhoneNumber:
StringThe company phone detailsmobilePhoneNumber:
StringThe mobile phone details of the companyjobDescription:
String!The Employer's job descriptionindustry:
Industry!The industry in which the company is categorisedlocation:
String!The address of the companyrecruiterDetails:
RecruiterDetails!The company's recruiter details
RecruiterDetails
The company recruiter details
id:
IDUnique id for each recruiter detailsfirstName:
StringThe recruiter's first namelastName:
StringThe recruiter's last namephoneNumber:
StringRecruiter phone numberemail:
StringRecruiter email addressjobTitle:
StringRecruiter job title
DashboardDeatils
This entity contains all the data needed to be in the analytics dashboard of the employer account
numberOfJobListing:
IntTotal number of jobs listed by the employernumberOfApplication:
IntTotal number of applications submitted to the employernumberOfAccepted:
IntTotal number of accepted jobs by employernumberOfRejected:
IntTotal number of rejected jobs employerjobListings:
JobList of all the job details listed by the employerallApplications:
ApplicationList of all the applications made to the employerpendingApplications:
ApplicationList of all the applications pending for the employer's reviewacceptedApplication:
ApplicationList of all the accepted applications made to the employerrejectedApplication:
ApplicationList of all the rejected applications made to the employer
Job
The job entity contains all the necessary details that make up the job.
id: ID Unique id for each job
jobTitle:
String!Job titlejobDescription:
String!Job descriptionworkMode:
enum [Remote, Hybrid, InPerson]The mode of workingskillRequirement:
String!The list of required skillsexperienceLevel:
String!A minimum level of experience requirementcertificates:
StringList of required certificatesacceptBackgroundChecks:
StringList of acceptable background criteriarejectBackgroundChecks:
StringList of rejectable background criteriarequireDocumentUrl:
StringList of required documents to be submitteddeadline:
Date!: Job application deadlinelocation:
String!Job locationminCompensation:
Stringminimum compensation for the jobmaxCompensation:
Stringmaximum compensation for the jobpublicizeSalary:
Booleanshows compensations for the job listing or notStatus:
enum[Active, Achieve]To categorize the job between active and archive
Application
This entity constitutes the job application made by an applicant to a particular job. This is accessible by the applicant and also the employer.
id:
IDUnique id of each applicationapplicant:
User(Applicant) The applicant detailsjob:
JobThe job detailsstatus:
ApplicationStatus [pending, accepted, rejected, interview, withdrawn]note:
StringRecruiter's note on the applicationmeetingScheduleDate:
DateMeeting schedule between applicant and employermeetingScheduleTime:
TimeObjectMeeting schedule between applicant and employer
Last updated
Was this helpful?