BuildClient

Hierarchy

• ResourceClient
  • BuildClient

Index

Properties

• apifyClient
• baseUrl
• httpClient
• id
• params
• resourcePath
• safeId
• url

Methods

• abort
• get
• waitForFinish

Properties

apifyClient

apifyClient: ApifyClient

Inherited from ResourceClient.apifyClient

baseUrl

baseUrl: string

Inherited from ResourceClient.baseUrl

httpClient

httpClient: HttpClient

Inherited from ResourceClient.httpClient

optionalid

id?: string

Inherited from ResourceClient.id

optionalparams

params?: Record<string, unknown>

Inherited from ResourceClient.params

resourcePath

resourcePath: string

Inherited from ResourceClient.resourcePath

optionalsafeId

safeId?: string

Inherited from ResourceClient.safeId

url

url: string

Inherited from ResourceClient.url

Methods

abort

• abort(): Promise<Build>

• https://docs.apify.com/api/v2#/reference/actor-builds/abort-build/abort-build

  ---

  Returns Promise<Build>

get

• get(options?: BuildClientGetOptions): Promise<undefined | Build>

• https://docs.apify.com/api/v2#/reference/actor-builds/build-object/get-build

  ---

  Parameters

  • options: BuildClientGetOptions = {}

  Returns Promise<undefined | Build>

waitForFinish

• waitForFinish(options?: BuildClientWaitForFinishOptions): Promise<Build>

• Returns a promise that resolves with the finished Build object when the provided actor build finishes or with the unfinished Build object when the waitSecs timeout lapses. The promise is NOT rejected based on run status. You can inspect the status property of the Build object to find out its status.

  The difference between this function and the waitForFinish parameter of the get method is the fact that this function can wait indefinitely. Its use is preferable to the waitForFinish parameter alone, which it uses internally.

  This is useful when you need to immediately start a run after a build finishes.

  ---

  Parameters

  • options: BuildClientWaitForFinishOptions = {}

  Returns Promise<Build>