Logo

How to use · one ticket at a time

Check this one first,then confirm the next step.

The extension only handles jobs you authorized in your match result. The flow is: read tickets, pick a job and a resume, check the relevant platform only if needed, then confirm. Nothing is applied in bulk by default.

Follow along now

From token to application receipt

  1. 01

    Generate and copy a token

    Go back to your Career Match result, click “Generate 7-day token”, then “Copy token”. Generating a new token invalidates the old one.

  2. 02

    Save the token to connect PageFlux

    Open “PageFlux Auto Apply Assistant” from the browser toolbar, paste the token into “Plugin token” and click “Save token”; continue once “Authenticated” shows in the top-right corner.

  3. 03

    Read tickets awaiting confirmation

    Click “Read pending tickets”. The list only shows job tickets for this token and applications whose status still needs reporting.

  4. 04

    Pick one job and a resume

    Choose one job at a time, then load the resumes available for that ticket. Check the job, company, platform and resume before moving on.

  5. 05

    Only check platforms that matter and need a login

    Read the ticket and select the job first, then decide whether its platform needs a login; only then open that job board and click “Check job board login”. Lever/Ashby public forms need no prior login.

  6. 06

    Confirm the application

    Click “Confirm application”. On Lever/Ashby the extension fills in the public form and waits for you to submit on the job page; on other platforms follow the extension's prompts for this job. Applications cannot be undone.

  7. 07

    Check the result, avoid repeating

    The extension reports success, rejection by the platform, or failure. If you see pending, a request id or “awaiting report”, keep the message and wait for it to recover instead of clicking again.

No tickets awaiting confirmation? Go back to your Career Match result, make sure the jobs are still authorized, then generate a new 7-day token and read the tickets again.

Platforms

Only the platform this ticket belongs to

Decide on login requirements after reading the ticket and selecting the job; there is no need to check unrelated platforms in advance.

Platforms that need a login

For Nowcoder, Zhaopin, Tencent, ByteDance and similar platforms, open the platform and check your login after selecting its ticket.

Lever / Ashby public forms

Public forms need no prior login. The extension fills in your details and waits for you to submit on the job page.

API protocol

Every step has a receipt

All endpoints use `Authorization: Bearer <Token>`. Tokens are valid for 7 days and only reach application endpoints; the extension keeps ticket_id, attempt_id and request id so work can resume.

  1. 01

    Read tickets

    GET /api/v1/plugin/delivery/queue

    Returns the selected tickets you can confirm under this authorization, plus dispatched ones that still need a report.

  2. 02

    Read this ticket's resumes

    GET /api/v1/plugin/delivery/tickets/{ticket_id}/application-materials

    Returns the application materials available for this job by ticket_id, so you can pick a resume before confirming.

  3. 03

    Authorize one application

    POST /api/v1/plugin/delivery/dispatch

    After you confirm the job and resume, submits the ticket_id and extension version; the server binds the job, resume and version again.

  4. 04

    Report the result

    POST /api/v1/plugin/delivery/report

    Submits the attempt's outcome, platform receipt and evidence; if the network drops or the status is unclear, the local record is kept for a later report.

When you are done

Head back to your match result and keep your job search going.

Open this match result