This script is still on early beta stage, so use it at your own risk.

iTunesConnect command line interface.

Script allows to add/edit metadata, uploads and in-app purchases of the application through iTunesConnect without user interaction.

Have you ever had to create 1000 inapp purchases by template? Or may be to upload 15 localized screenshots for each of 25 languages you app supports? This script does that for you :)
_{This is my first ever application written in python, so, please don't judge me too harshly ;)}

itc.cli is available under the MIT license.

• Download sources somewhere on your computer
• sudo python setup.py install

• Download sources somewhere on your computer
• Install dependencies: lxml, html5lib, requests
• export PYTHONPATH=${PYTHONPATH}:/path/to/itc.cli/source/directory
• export PATH=${PATH}:/path/to/itc.cli/source/directory/itc/bin

Now itc command is available to run

itc --username apple_id --password my_password

--password parameter is not mandatory, so you can input password manually after script startup

If all dependencies installed properly, you will see something like this:

itc --username apple_id

Password:
INFO:root:Login: logged in. Session cookies are saved to .itc-cli-cookies.txt
INFO:root:Application found: "App 1" (123456789)
INFO:root:Application found: "App 2" (987654321)
INFO:root:Nothing to do.

Every time you run the script, it uses cookies which are stored in the file .itc-cli-cookies.txt and checks if cookies are still valid or script needs to log in again. That means that once you've entered your password, you don't need to enter it anymore as long as session is alive on iTunesConnect's servers.

Party begins with --config_file parameter:

itc --username apple_id --config-file actions.json

Config file is a simple JSON file (please note, that it's a strict JSON. You must avoid constructions like ,] or ,} (i.e. [1,2,] or {"a":"avalue", "b": "bvalue",}). If your config file contains errors, you'll get an exception with the exact position of a wrong character)

Commands object has two fields - 'general' and 'languages'. Script merges each language's object with 'general' object. For example:

{
  "general" : {
      "name"               : "My application - default",
      "whats new"          : "What's new - default"
  },
  "languages" : {
      "en" : {
          "whats new": "What's new - en"
      },
      "pt" : {
          "name"     : "My application - pt"
      }
  }
}

In the example above the following values will be assigned:

For English language:

"name"               : "My application - default",  
"whats new"          : "What's new - en"

For Brasilian Portugese:

"name"               : "My application - pt",  
"whats new"          : "What's new - default" 

You can also use files as a source of data for "whats new", "description" and "keywords":

  "general" : {
      "name"               : "My application - default",
      "whats new"          : {"file name format": "app data/whats new - {language}.txt"},
  }

So, itc.cli during iteration through languages will replace {language} with appropriate language id (i.e. "pt", "en" and so on).

Now the most interesting part - images. Images object contains three fields:

• iphone
• iphone 5
• ipad

Each field's value is an array of commands (well, in 99% of cases you'll need only one command).

There are four commands for updating images:

• Delete ('d')
• Upload ('u')
• Sort ('s')
• Replace ('r')

If indexes are provided, deletes images by selected indexes. Otherwise deletes all images

Uploads images. If indexes are provided, only images with selected indexes will be uploaded

Sorts images. indexes are mandatory for this command

Replaces existing images with new ones. If indexes are not provided, deletes all images and uploads new ones

There's an option in config section:

{
    "images": {
        "file name format": "images/{language}/{device_type} {index}.png"
    }
}

Imagine you have the following folder structure:

itc.cli.git\
    images\
        en\
            iphone 2.png
            iphone 5 2.png
            ipad 4.png
        pt\
            iphone 1.png
            iphone 2.png
            iphone 3.png
            iphone 4.png
            iphone 5.png <- 5th screenshot for 3.5" iPhone
            iphone 5 1.png <- 1st screenshot for 4" iPhone
            iphone 5 2.png
            ipad 1.png
            ipad 2.png
            ipad 3.png
            ipad 4.png

So, if you write the following command:

"ipad": [{"cmd": "u"}]
One iPad screenshot will be uploaded for English language and four for Portugese. Please, note that you have to make sure that there are enough space for these screenshots.

"iphone": [{"cmd": "r"}]
This command replaces second screenshot for English language and replaces all screenshots for Portugese.

Of course for each language you can specify exact indexes of replaced/deleted and uploaded screenshots:

{
  "general" : {
      "images": {
          "iphone"  : [{"cmd": "d", "indexes": [3]}],
          "iphone 5": [{"cmd": "r"}],
          "ipad"    : [{"cmd": "u"}]
      }
  },
  "languages" : {
      "en" : {
          "images": {
              "iphone"  : "", <- don't modify iPhone screenshots for English language
              "iphone 5": [{"cmd": "u", "indexes": [2]}] <- instead of replacing all screenshots for iPhone 5, upload one with name 'iphone 5 2.png'
          }
      },
      "pt" : {
          "images": {
              "iphone": [{"cmd": "s", "indexes": [1, 3, 5, 4, 2]}] <- apply new sorting
          }
      }
  }
}

In the example above, all iPad and pt/iPhone 5 screenshots will be uploaded by generic rule. The rest are specific for each language.

With --generate-config parameter script creates json file ({application_id}.json), which contains metadata for each language of the application. In case if no --application-id parameter passed to script, it iterates through all the applications for current account.

At the moment, 4 of 5 inapp types are supported: 'Consumable', 'Non-Consumable', 'Free Subscription', 'Non-Renewing Subscription'

There are two ways of managing inapps. The first one is one by one:

[{       
  "id": "ru.kovpas.itc.cli.test.1.inapp.1",
  "type": "Non-Consumable",
  "reference name": "Test inapp",
  "price tier": 2,
  "cleared": false,
  "hosting content with apple": false,
  "review notes": "Notes",
  "review screenshot": "images/inapp.png",
  "general": {
    "name": "Test inapp",
    "description": "Description inapp",
    "publication name": "Publication inapp" <- only used for appropriate inapps 
  },
  "languages": {
    "en": {
      "name": "Test inapp - en",
      "description": "Description inapp - en",
    },
    "ru": {
      "publication name": "Publication inapp - ru"
    },
    "pt": {
      "description": "Description inapp - pt",
    }
  }
}, {2nd inapp}, {3rd inapp}, ...]

The second one is by using templates.

{
  "index iterator": {
    "indexes": [19, 20, 22]
  },
  "id": "ru.kovpas.itc.cli.test.1.inapp.{index}",
  "type": "Non-Renewing Subscription",
  "reference name": "Test inapp - {index}",
  "price tier": {
    "19-20": 1,
    "22": 2
  },
  "cleared": false,
  "hosting content with apple": false,
  "review notes": "Notes",
  "review screenshot": "images/inapp.png",
  "general": {
    "name": ["My first inapp", "My second inapp", "My third inapp"],
    "description": {
      "19": "My first inapp description",
      "20": "My second inapp description",
      "22": "My third inapp description"
    },
    "publication name": "Publication inapp - {index}"
  },
  "languages": {
    "en": {
      "name": ["My first inapp - en", "My second inapp - en", "My third inapp - en"],
      "description": "Description inapp - {index} - en",
    },
    "ru": {
      "publication name": "Publication inapp - {index} - ru"
    },
    "pt": {
      "description": "Description inapp - {index} - pt",
    }
  }
}

Script iterates through indexes array and creates inapp purchase. For the example above 3 inapps will be created.

Every {index} keyword in strings is replaced by corresponding index.
Arrays and dictionaries are also supported, so you could provide an array or dictionary instead of string. See example above for format reference.

Another way is to create start and end indexes:

{
  "index iterator": {
    "from": 7,
    "to": 9
  }
}

If from index is not provided, 1 is used. to index is mandatory.

There are several features planned to be implemented:

• inapp purchases management
• promo codes
• sales reports
• user reviews