getlulu-dev Cron API

The Cron API from getlulu-dev — 5 operation(s) for cron.

Operations 5

POST /cron/travelpayouts-poll Travelpayouts Poll #
POST /cron/adsterra-poll Adsterra Poll #
POST /cron/prospect-pitch-check Prospect Pitch Check #
POST /cron/poc-followup Poc Followup #
POST /cron/outreach-followup Outreach Followup #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/getlulu-dev:getlulu-dev-cron-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

getlulu-dev-cron-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Lulu Ads Cron API
  version: 0.1.0
tags:
- name: Cron
paths:
  /cron/travelpayouts-poll:
    post:
      summary: Travelpayouts Poll
      operationId: travelpayouts_poll_cron_travelpayouts_poll_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Cron
  /cron/adsterra-poll:
    post:
      summary: Adsterra Poll
      operationId: adsterra_poll_cron_adsterra_poll_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Cron
  /cron/prospect-pitch-check:
    post:
      summary: Prospect Pitch Check
      operationId: prospect_pitch_check_cron_prospect_pitch_check_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Cron
  /cron/poc-followup:
    post:
      summary: Poc Followup
      description: 'Daily: any publisher whose POC terms have passed their end date gets

        exactly one admin follow-up email ("POC ended — time to check in").

        The sent-flag is only written after a CONFIRMED send (same posture as

        prospect_pitch_check), so a failed email retries tomorrow instead of

        silently marking done.'
      operationId: poc_followup_cron_poc_followup_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Cron
  /cron/outreach-followup:
    post:
      summary: Outreach Followup
      description: 'Daily: two independent status transitions for mcp_owner_outreach,

        neither of which happened anywhere before this endpoint existed --

        every row past ''contacted'' required someone to notice and update it

        by hand.


        1. Reply detection: any ''contacted'' row with a real issue_url (wave 3

        onward -- waves 1-2 predate the column and are skipped, not

        guessed at) gets checked for a comment from anyone but us.

        2. Conversion detection: any ''contacted''/''replied'' row whose target

        mcp_servers row has since gained an ad_publisher_id (someone from

        that repo actually signed up) gets marked ''converted''.


        One digest email if anything changed; silent if nothing did (same

        "don''t alert on nothing" posture as prospect_pitch_check).'
      operationId: outreach_followup_cron_outreach_followup_post
      parameters:
      - name: authorization
        in: header
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Authorization
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Cron
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError